Methods and apparatus for providing expanded telecommunications service

ABSTRACT

The present invention provides flexible call processing. For example, a call processor system can receive an inbound call intended for a called party and place an outbound call to the called party. The call processing system can provide the called party with a call transfer option.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to telecommunications and in particular to systems and methods for processing and placing telephone calls.

2. Description of the Related Art

Many telephone subscribers have a personal computer on their desk and frequently the personal computer is logged in to the same telephone line that would normally be used by the telephone. This is for use of the computer on the Internet. Frequently, incoming telephone calls receive a busy signal because the computer is logged on to the Internet. Thus there are many lost calls. Many individuals and small businesses are searching for ways to simplify and control their telecommunications systems. Many of them are reluctant to acquire additional telephone lines at current prices.

Many telecommunications systems today have limited intelligence. Many calls end in voice mail, an often unsatisfactory conclusion. With respect to business calls, calls not completed may result in irritated customers and lost sales.

In addition, people are increasingly associated with a multiplicity of communication devices. For example, an individual may have a work phone, a home phone connected to a switched telephone network, a phone connected to an Internet protocol network, and a cellular phone.

SUMMARY OF THE INVENTION

The present invention relates generally to telecommunications, and more particularly to telephone call processing. By way of example and not limitation, several example embodiments will be described.

An example embodiment provides a method of processing calls, the method comprising: storing in computer readable memory associated with a call processing system a first phone address associated with a first subscriber; storing in computer readable memory a plurality of phone addresses for the subscriber associated with at least one network selected from the group including a wireline network, a wireless network, and/or an Internet network; participating at the call processing system in a first call with the subscriber, wherein the first call is associated with a second phone address; placing a first outcall from the call processing system to the first called party, wherein the call processing system inserts the first phone address in a callerID field associated with signaling information associated with the first outcall, wherein the first phone address is different than the second phone address; bridging the first call and the first outcall; participating at the call processing system in a second call with the subscriber, wherein the second call is conducted via a subscriber communication device associated with a third phone address; placing a second outcall from the call processing system to the second called party, wherein the call processing system inserts the first phone address in a callerID field associated with signaling information associated with the second outcall, wherein the first phone address is different than the third phone address; and bridging the second call and the second outcall.

An example embodiment provides a method of processing calls, the method comprising: receiving at a call processing system a first call request from a client telecommunications application hosted on a user computer, wherein the first call request identifies a first party to be called; at least partly in response to the first call request, placing a first outcall from the call processing system to a telephone associated with the user; placing a second outcall from the call processing system to a telephone associated with the first party, wherein the second outcall is associated with signaling information, the signaling information including a user phone address associated with the user, wherein the user phone address is not the phone address of the call processing system, but is a phone address assigned to or specified by the user; and causing the first outcall and the second outcall to be connected.

Still another example provides a method of processing calls, the method comprising: storing in computer readable memory an association between a user and a first phone address associated with a call processing system; receiving from the user a plurality of user phone addresses associated with at least one network selected from the group including wireline network, wireless network, and Internet network; storing the plurality of user phone addresses in computer readable memory; receiving at the call processing system an indication from the user that the user want to establish a call with a first party using a first of the plurality of phone addresses; and placing a first outcall from the call processing system to the first party, wherein the call processing system inserts the first phone address associated with the call processing system in a callerID field associated with signaling information corresponding to the first outcall, wherein a user communication device to be connected to the first outcall at least partly in response to a user action.

An example embodiment provides a method of processing calls, comprising: receiving at a call processing system a message from an Internet protocol proxy regarding a first call from a caller; determining if the first call is directed to a telephone address of a subscriber of services offered by the call processing system, wherein at least partly in response to determining that the telephone address is that of a subscriber: accessing an account record associated with the subscriber, the account record including at least one subscriber instruction; based at least in part on the subscriber instruction, placing a first outcall to a first communication device associated with the subscriber; if the first outcall is not answered within a first number of rings or period of time, placing a second outcall to a second communication device associated with the subscriber; and receiving a call connect instruction from the subscriber; and instructing the call processing system to connect the first call to a third communication device.

An example embodiment provides a method of processing calls, comprising: receiving a message over the Internet indicating a call has been placed by a caller to a phone address of a user having a mobile communication device, wherein the user has an account associated with a call processing system; requesting the status of the mobile communication device; receiving a response to the request; if the response indicates that the mobile communication device is available to receive the call, causing at least in part that call to be routed to the mobile communication device; receiving at the call processing system an indication as to whether the mobile communication device answered the call; at least partly in response to receiving an indication that the mobile communication device answered the call, causing a half-duplex talk path to be established between the mobile communication device and the caller so that the subscriber can hear the caller and the caller does not hear the subscriber; at least partly in response to receiving an indication that the subscriber wants to converse with the caller via the mobile communication device, causing a full duplex communication path to be established between the mobile communication device and the caller; connecting the call to a computer-based telecommunications client application in half-duplex mode, wherein the subscriber can hear the caller and the caller cannot hear the subscriber; and if an indication is provided that the subscriber wants to converse with the caller via the computer-based telecommunications client application, causing, at least in part, a full duplex talk path to be established between the computer-based telecommunications client application and the caller so that the caller and the subscriber can converse.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described with reference to the drawings summarized below. These drawings and the associated description are provided to illustrate example embodiments of the invention, and not to limit the scope of the invention.

FIG. 1 is a schematic representation of one embodiment of the present invention.

FIG. 2 is an example of a typical screen for a control panel.

FIG. 3 is a more detailed version of the communication path of the system of the present invention.

FIG. 4 is a schematic diagram of the call handling process.

FIG. 5 is the process of locating the subscriber.

FIG. 6 is an expansion of FIG. 3 showing how a Telco central office can be connected by way of wireless connections or by way of land line connections to the server.

FIG. 7 is a sequence of steps on a flow chart indicating the handling of a call.

FIG. 8 is a flow chart showing a series of steps in the handling of incoming telephone calls.

FIG. 9 is a flow chart illustrating further steps in the call handling flow chart.

FIG. 10 is a sequence of steps in a flow chart.

FIG. 11 is a flow chart for steps in deciding how the subscriber answers a call.

FIG. 12 illustrates calling back into the central server while an incoming call is being held at the server.

FIG. 13 is a sequence of steps in a method flow chart illustrating capturing the dynamic profile of a subscriber.

FIG. 14 is a schematic diagram indicating how the system can handle undesired incoming calls.

FIG. 15 is a schematic diagram illustrating a second embodiment of the call control system of the present invention.

FIG. 16 illustrates an example telecommunications system that can be used in accordance with one embodiment of the present invention.

FIG. 17 further details the subsystems that comprise the IAM system depicted in FIG. 16 described above.

FIG. 18 displays an example menu of call screening/handling options available to the called party during the processing of the inbound call.

FIGS. 19A-19B illustrate a first example call screening process in accordance with the present invention.

FIGS. 20A-20B illustrate a second example call screening process in accordance with the present invention.

FIG. 21 illustrates an example call transfer process.

FIG. 22 illustrates a call transfer process with respect to the caller.

FIG. 23 illustrates a call transfer process with respect to the called party.

FIG. 24 illustrates another call process.

FIGS. 25A-B illustrate another call process exemplifying the use of Location Based Services.

FIG. 26 illustrates an example call transfer process using auto-callback.

FIG. 27 illustrates a first example call flow.

FIG. 28 illustrates a second example call flow.

FIG. 29 illustrates a third example call flow.

FIG. 30 illustrates a fourth example call flow.

FIG. 31 illustrates a fifth example call flow.

FIG. 32 illustrates a first example user interface.

FIG. 33 illustrates a first example user interface.

FIG. 34 illustrates a first example user interface.

FIG. 35 illustrates a first example user interface.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the present invention are directed methods and systems for providing call screening and/or call forwarding/transfer in conjunction with a variety of network-based telephone call answering processes and services.

FIG. 1 is a schematic representation of the organization of one embodiment of the present invention. FIG. 1 shows a first entity 20 connected to the Public Switched Telephone Network (PSTN) 21. A second entity 22 is also connected to the PSTN 21. The second entity 22 is illustrated as having a first device 23 indirectly connected to the Internet 26 through a PSTN 21 provided dial-up connection shared with the telephone of the second entity 22. The second entity 22 is also shown to have a second device 24 directly connected to the Internet 26. Both devices host a software based Command Center 25. The devices may or may not be logged onto the Internet 26. FIG. 1 also shows a local exchange switch 27 connected to the PSTN 21. The system directs the call and the call information of the first entity 20 through the PSTN 21 to the local exchange switch 27 and then to a gateway 28; said gateway can be implemented as a local gateway 28A near the switching system 27 or a centralized gateway 28B near the server 29. The gateway forwards the call information to the Server (or array of Servers) 29 which then communicates to the Command Center 25 over an Internet Protocol connection that is by a plurality of means, including a single phone line dial up connection (e.g. as shown in the case of the first device 23) an always on landline home connection (for example as shown in the case of the second device 24) an always on landline office connection or an always on wireless connection. The Server 29 and the Command Center 25 then interact to coordinate the dialog with the first entity 20 over the PSTN 21 and the second entity 22 over the appropriate device 23 or 24.

Referring now to FIG. 2 of the drawings, an example of a typical screen for command center 25 a control panel is shown. It should be understood that the control panel may have messages on it other than the ones shown in the figure. The control panel of FIG. 2 would typically show up in a small area of the monitor screen of the subscriber's device desktop (e.g. computer) 23 & 24. For example, the control panel of FIG. 2 may occupy only a 1 inch by 2 inch corner of the screen. The control panel of FIG. 2 displays status of the incoming call and allows the second entity 22 to coordinate interactions with the server 29. The command center interface supports a plurality of call control inputs including a) no input b) transfer call over circuit switching network c) take call over Internet Protocol d) reoriginate the call over circuit switched or Internet Protocol network e) have the server interact with the caller to provide information or record the audible signal.

Referring now to FIG. 3 of the drawings, there is shown a more detailed version of the communication path of the system of the present invention. An incoming call is illustrated as being directed to a home telephone number 30 in the Plain Old Telephone System (POTS) which is passed on to the POTS Network 31. The POTS Network 31 is shown connected to a Signaling System 7 (SS7) 32. The telephone system employs what is known as Common Channel Signaling (CCS). This is a signaling system used in telephone networks that separates signaling information from user data. A specified channel is exclusively designated to carry signaling information for all other channels in the system. The SS7 32 is one of the standard CCS systems used by the telephone company. The SS7 32 is connected to the central server 28. The SS7 32 normally connects between central offices. Because the present invention uses the SS7 32, it appears to be a central office to the telephone companies. The system can be or act as a class 5 telephone office. A message store memory 33 is located at the central server 29 for storing messages. The central server 29 communicates through the internet 26 to the personal desktop computer 25 of the client. The central server 29 is shown as also communicating to a second client having a personal desktop computer 34. A call merger 39 connects from the Internet 26 to a telephone instrument.

When an incoming call comes in to the home telephone number 30, the central server 29 interacts with the caller. It makes a record of the caller's telephone number or prompts the caller to unblock the telephone so as to give the caller's telephone number. The central server 29 may give the caller options that can be answered by a touch tone response, or it may ask for a voice message to be passed on to the subscriber. If an audio message is given to the central server 29, that message is passed along using Voice Over IP (VOIP) which is used in the telephone system and over the internet. The letters IP stand for Internet Protocol.

Teleconferencing over the internet is done using a standard developed by the International Telecommunications Union (ITU). This standard is known as ITU-T H.323. This provides for audio and video in a teleconferencing context. From the standpoint of VOIP, the video component of the teleconferencing signal is ignored and only the audio is used. This permits audio to be transferred from the incoming call at the home telephone number 30 to the client's personal desktop computer 25. The client can listen to the message from the incoming call before making a decision as to the handling of the call. The server communicates to a command center running on a multiplicity of platforms and providing a control interface to the second entity. The command center is a software and device solution that can be hosted alternatively on a personal computer, a handheld computing device, a wireless telephone, a television, a web interface appliance, or a command center server using voice and DTMF tone interaction with a telephone device.

Referring now to FIG. 4, there is shown a schematic diagram of the call handling process. Box 35 indicates the arrival of an incoming call. The options may include forward the call, call forward no-answer, forward the call always, and it may provide for switching the call to a different telephone number, for example that of a cell phone or other device. The caller may be presented with voice mail type options. For example, if you wish to talk with Mr. Jones, press 1, if you wish to talk with Mrs. Jones press 2, if you wish to talk with Susie Jones press 3. The caller may be required to give a touch tone ID, or to provide a touch tone ID of the called party. The dialog process is for the purpose of obtaining as much information as possible as to who is calling, which family member is being called, and why. The caller may be asked to speak a message into the telephone as would be done with an answering machine. This message is recorded and passed on to the subscriber so that he can listen to it to aid him in making the call handling decision. As shown at box 37, the caller's telephone number is noted by the central server 29, or the caller is prompted to unblock the telephone number. Box 36 indicates that a dialog is conducted by the central server 29 with the caller. Box 38 shows the call handling decision. The system identifies the first entity by the following methods: detecting caller ID and or called number information from the call information received from the switch, by means of voice prompts from the system and tone response from the first entity by which the first entity identifies their number, or the person whom they are calling, or by means of capturing an audible signal from the first entity.

The central server 29 may go through a process of locating the subscriber. This is illustrated in FIG. 5. This service is sometimes referred to as find me/follow me. As indicated in FIG. 5, the subscriber may have his home number logged on line for the Internet as indicated in block 40. However, the subscriber may have an additional home number as shown in block 41 or the subscriber may have a business number as shown in block 42. The subscriber may have a personal number as in block 43, or a special number classed as a single purpose number as in block 44. In addition the subscriber may have a cell phone 45 or a pager 46.

It should be understood that as the central server 29 goes through the processes of locating the subscriber, the caller is not aware of any of the procedures that the central server 28 is going through. The caller is unaware of any of the special numbers that the subscriber may have, or equipment such as pagers or cell phones.

It is not necessary for the equipment used by the system such as the central server 29 to be located close to the subscriber or close to the called number. For example, as shown in FIG. 6, the POTS Network 31 can be connected through a Telco central office 47 via the SS7 32 by way of wireless connections 48 or by way of land line connections 50 to the server 29 at a remote location.

It should be understood that the message store memory 33 shown in FIG. 3 may include a list of numbers that the subscriber wishes to speak to always. These may be family members, or business partners, or the like. These may be added to at the subscriber's discretion. Other instructions for call handling may be recorded in the message store memory 33. One of the first things done by the central server 29 is to check to see if there are special instructions for handling of a given incoming call. FIG. 7 shows a sequence of steps on a flow chart indicating the handling of a call. The first box 51 is “begin”. Box 52 is “placing a call from a first entity to a second entity”. Box 53 is “receiving the call at a local exchange switch”. The next step is shown in box 54 as “identifying a number of the first entity”. Box 55 is “directing the call and the number of the first entity to a gateway”. Box 56 is “directing the call, call information, and the number of the first entity to a server”. Box 57 is “determining whether the Command Center of the second entity is communicating with the server”. Box 58 is “sending a message to the Command Center indicating the presence of a call and identifying the number of the first entity and the number of the second entity”. Box 60 is “directing the call to one of a plurality of telephonic devices according to the number of the second entity” and the last block on FIG. 7 is box 61 “end”.

FIG. 8 is a flow chart showing a series of steps in the handling of incoming telephone calls. The first block 62 is “begin”. Block 63 is “receiving at the server a command from the command center to have the server answer the call”. Block 64 is “answering the call through the server”. Block 65 is “playing a message”. Block 66 is “recording a message from the call”. Block 67 is “storing the message from the call in the server”. The last block is 68 “end”.

FIG. 9 is a flow chart illustrating further steps in the call handling flow chart. The first block 70 is “begin”. Block 71 is “determining whether special instructions are stored in the computer regarding forwarding calls”. Block 72 is “forwarding the call to a number designated by the second entity”. Block 73 is “end”.

As has been indicated hereinbefore, an audible message from the caller may be played to the subscriber to aid him in making a decision for handling the call. However, the subscriber may also record messages, and these messages may be played to the caller as well. There may be a number of different messages depending upon the circumstances, and these may be selectively played as desired. Referring now to FIG. 10, there is shown a sequence of steps in a flow chart. Block 74 is “begin”. Block 75 is “recording a plurality of different audio greetings”. Block 76 is “storing said audio greetings in a memory storage device”. Block 77 is “playing a preselected one of said audio greetings to a caller on demand”. Block 78 is “end”. Referring now to FIG. 11, this Figure shows a flow chart for steps in deciding how the subscriber answers a call. The first block 80 is “begin”. Block 81 is “developing a data base of important telephone numbers”. Block 82 is “answering a call by the server only if the line is busy and the caller number is in the data base”. Block 83 is “permitting the subscriber to monitor a message from the caller audibly over the Internet”. Block 84 is “permitting the subscriber to make a decision how to handle the call over the Internet”. Block 85 is “permitting the subscriber to specify: always, or this time only, connect the call, transfer the call, take a message, or terminate the call”. Block 86 is “end”.

The client or subscriber has many ways to deal with an incoming call. He can elect not to answer and to take a message, or he can have the call played through the personal desktop computer 25 and talk to the caller via the Internet 26, or he can have the call transferred to a different instrument such as a second telephone 24 (FIG. 1) or a cell phone 45 (FIG. 5). There is another way for the subscriber to handle a call. While the central server 29 is holding the call, the client can pick up a cell phone or a regular POTS phone and call in to the central server 29 and have a call cross-connect right there. This is illustrated in FIG. 12. This Figure illustrates an incoming call arriving at the central server 29. It is connected to the Internet 26 and to the client's personal desktop computer 25. Then, the client may elect to make a POTS inbound call to the server 87. This means, for example, picking up a cell phone or a regular POTS phone and dialing the number to the central server 29. At the central server 29, a call cross-connect is made, and the client can talk to the caller making the incoming call.

The central server 29 is able to capture and store the dynamic profile of the subscriber's rules for treatment of incoming calls. This is illustrated in FIG. 13. FIG. 13 is a sequence of steps in a method flow chart. Block 90 is “begin”. Block 91 is “monitoring and screening incoming calls based on properties such as call type, caller number, called number, time of day, family member called”. Block 92 is “locating subscriber using find me, follow me, first or second home phone, business phone, cell phone and various Internet devices”. Block 93 is “allowing subscriber to specify call treatment, e.g., connect the call, transfer the call, take a message”. Block 94 is “observing and noting subscriber treatment of call”. Block 95 is “profiling dynamically call treatment by subscriber”. Block 96 is “reviewing by subscriber of suggested call handling rules”. The subscriber is not asked to enter his rules for handling calls but rather the subscriber is presented with rules determined implicitly by the central server 28. The subscriber then has an opportunity to approve or to reject the proposed rules. Block 97 is “capturing and storing dynamic profile of subscriber call treatment”. This dynamic profile may be stored in the message store memory 33 of the central server 28. In addition an address book may be compiled at that same location so that if the subscriber wishes to place a call, or to return a call following a telephone message, it is easy to initiate using the numbers logged in the address book in the message store memory 33 of the central server 28. In FIG. 13, the last block 98 is “end”.

The central server 28 of the system of the present invention gradually becomes more useful to the subscriber as it learns the subscriber's profile. This profiling also adds another dimension to the system of the present invention. This is an advertising or media dimension. The profiling creates a community of users. People that call each other on the telephone have a community of interests. Thus the profiling information that is stored becomes, in effect, a collaborative filter based on telephone numbers. Recording of calls made to other numbers indicates similar patterns of behavior. This is based on shared interests. Thus, this gradual interactive development of a profile based on decisions made by the client may be used for advertising purposes, if desired.

FIG. 14 is a schematic diagram indicating how the system can handle undesired incoming calls. At the left of FIG. 14 there is illustrated an incoming call 35. The call is coupled to a detector for detecting phone “spam” 100. The incoming call 35 is also connected to a detector for detecting nuisance calls 101. Both of these types of telephone calls are unsolicited, unwanted, and undesirable types of calls. When these types of calls are detected, they are forwarded to block 102 which initiates a “rude” hang-up. This type of hang-up would have an audible message to the caller saying something such as “never call again”. Then, the signal is passed on to block 103 which terminates the call.

Typically, the system only answers calls for the client when the client's telephone line is busy and he is logged on the Internet. However it can be arranged for the system to answer all of the client's incoming calls. This is illustrated in FIG. 15. FIG. 15 is a schematic diagram illustrating a second embodiment of the call control system of the present invention. In this embodiment of the invention, the hard connection from the POTS to the subscriber is broken. This is done by the central server system providing a virtual phone number to the client without providing a telephone instrument. This is illustrated in block 104. The virtual telephone number is given to the client who optionally uses it in his advertising so that all calls will be made to that number but in fact those calls will be intercepted by the system of the present invention.

Throughout the following description, the term “Web site” is used to refer to a user-accessible network site that implements the basic World Wide Web standards for the coding and transmission of hypertextual documents. These standards currently include HTML (the Hypertext Markup Language) and HTTP (the Hypertext Transfer Protocol). It should be understood that the term “site” is not intended to imply a single geographic location, as a Web or other network site can, for example, include multiple geographically distributed computer systems that are appropriately linked together. Furthermore, while the following description relates to an embodiment utilizing the Internet and related protocols, other networks, such as networked interactive televisions, and other protocols may be used as well. In addition, unless otherwise indicated, the functions described herein are preferably performed by executable code and instructions running on one or more general-purpose computers. However, the present invention can also be implemented using special purpose computers, state machines, and/or hardwired electronic circuits. In addition, a communications line is referred to as “busy” when the communication line is being utilized in such a way that a conventional incoming call will not be connected to the communications line. Thus, for example, if a user is utilizing a conventional line capable of only conducting one of a conventional voice session and a data session, but not both at the same time, for a data session, the line will be busy. With respect to the example processes disclosed herein, not all states need to be reached, and the states do not necessarily need to be performed in the same order as that illustrated. Unless otherwise specified, the term phone number refers generally to a telephonic address, such as, without limitation, a standard POTs telephone number, an E.164 phone number (ITU-T recommendation which defines the international public telecommunication numbering plan and telephone format used in the PSTN and certain data networks), or a VoIP address.

FIG. 16 illustrates an example telecommunications system that can be used in accordance with the present invention. As illustrated, the telecommunications system includes:

-   -   a plurality of user telephone stations 1102, 1112.     -   a plurality of user computer terminals 1110.     -   a call processing system 1124 that acts as an Internet Answering         Machine (IAM) system.

These devices are linked together using various line and trunk circuits to a Public Switched Network (PSTN) 1104 and to a common data network, such as the Internet 1106.

FIG. 17 further decomposes the JAM system 1124 into its functional components:

-   -   a Call Management (CM) subsystem 1108, which serves as the         interface to the PSTN 1104 to manage inbound and outbound         telephone calls.     -   a Router subsystem 1140, which serves as the interface to the         Internet 1106 to manage communications between online IP client         devices and the various JAM servers.     -   an online presence detection Internet Session Management (SM)         subsystem 1122, which monitors the status of subscriber data         terminals to determine availability for call handling services.     -   a shared Media Storage (MS) subsystem 1138, which persistently         archives the caller's voice messages and the called         party/subscriber's personal greeting(s).     -   an JAM Database (DB) subsystem 1136 in which called         party/subscriber JAM service parameters are stored.

These various subsystems are interconnected via a Local Area Network (LAN) and/or via a Wide Area Network (WAN). CallWave, Inc. operates one such JAM system. As is well known in the field of Internet telecommunications, an JAM service works with the “Call Forward On Busy” feature of a standard phone line to answer calls while the subscriber is online and is using the phone line to access the Internet. Once activated, callers no longer get annoying busy signals when the subscriber is online. Instead, callers hear a brief greeting after which they can leave a short message. The recording can be streamed in substantially real-time or sent to the subscriber over the Internet within seconds after the recording has completed. Just like a home telephone answering machine, the subscriber can elect to interact with the caller while they are still on the line or can call them back at a later time.

Referring back to FIG. 16, the user telephone stations 1102, 1112 are respectively connected to local exchange switches 1126, 1128 via telephone lines 134, 1114. The stations 1102, 1112 can optionally be conventional POTS (Plain Old Telephone Service) telephones or local extensions behind a corporate Private Branch Exchange (PBX), or can be wireless cellular phones connected via a cellular or other wireless network.

The telephone stations 1102, 1112 can be coupled to the same switch or different switches. If the telephone stations 1102, 1112 are coupled to the same switch, the switch will be local to both the calling and called parties, such as for intra-LATA or local calls. If telephone stations 1102, 1112 are coupled to different switches, each switch may be local only to one of the parties, as is the case for non-local calls such as inter-LATA (long-distance) calls. The PSTN can be configured to handle mobile, wireless stations via wireless communications towers configured to broadcast and receive cellular radio frequency communications. The wireless towers can be, for example and without limitation, CDMA or GSM cellular mobile base stations.

In the illustrated embodiment, the CM subsystem 1108 is coupled into the PSTN 1104 through voice trunk circuits 1118 directly interfacing with the Inter Exchange Carrier's (IXC) circuit switched or packet switched telephony network. Thus, advantageously the IAM system 1124 does not have to be directly serviced by the same Local Exchange Carrier's (LEC) switch or PBX as the calling or called terminals 1102 and 1112. Indeed, the JAM system 1124 or its individual subsystem components can be located in a different country than the called and calling parties. In this instance, the IAM system 1124 is optionally configured as, or to appear as, a telephone end office and can interface with the PSTN 1104 as a Class 5 switch. In other embodiments, the IAM system 1124 is locally attached to a LEC switch with a physical line or local trunk interface circuit. This switch may or may not be serving telephone stations 1102 and/or 1112.

The IAM voice trunk circuits 1118 are not limited to a particular signaling convention. For example, the present invention can be utilized with a Common Channel Signaling system, such as Signaling System 7 (SS7), having separate voice/user data and signaling channels. In addition, the present invention can be used with other signaling methods, such as the following trunk-side signaling interfaces: ISDN-PRI; Advanced Intelligent Network; and/or Service Node architectures. Preferably, the selected signaling system provides a suite of call presentation information to the IAM system 1124, including one or more of:

-   -   ANI—Automatic Number Identification: phone number and privacy         indicator of the calling party (“Caller-ID”).     -   DNIS—Dialed Number Identification: phone number of the JAM         system's voice trunks 1118 that the call was forwarded to.     -   OCN—Original Called Number Identification: phone number of the         original called party (subscriber to the IAM service).     -   Call Type—Forwarded call due to a BCF, RNA, or DND/CFA         condition. In addition, directly dialed inbound calls can be         handled as well. In this instance, the caller will be required         to implement a second stage of dialing to enter the subscriber's         phone number or the subscriber could be assigned a unique         personal number that is directly dialed by their callers.

The telephone lines 134, 1114 may be shared with one or more computer terminals. For example, telephone terminal 1112 shares the telephone line 1114 with a computer terminal 1110. While in the illustrated example the computer terminal 1110 is a personal computer, the computer terminal 1110 can be an interactive television, a networked-enabled personal digital assistant (PDA), other IP (Internet Protocol) device, or the like. Alternatively, the computer terminal 1110 can be a personal computer having a monitor, keyboard, a mouse, a disk drive, sound card or similar sound reproduction circuitry such as a codec, streaming media playback software, such as the Media Player program available from Microsoft, speakers, and a modem, such as a standard V.90 56K dial-up modem. The modem can optionally be configured to dial-up a number under control of an application, such as a contact manager application or telecommunications client application phone dialer, stored and executing on the computer terminal 1110.

The telephone line 1114, can be used to establish a dial-up connection for computer terminals, such as terminal 1110 via the computer modem, to an Internet Service Provider (ISP) offering dial-in remote access service connections from the PSTN 1104 via trunk interface circuits 1120. The computer terminal 1110 can also be connected to the Internet 1106 via a broadband connection, such as a DSL line, a television cable line, or a T1 line.

In addition, the computer terminal 1110 can be equipped with a Voice over Internet Protocol (VoIP) software module and a headset or a handset 1132, including a microphone and speaker, allowing voice communications to be conducted over a computer network, such as the Internet 1106. VoIP communicates information via packet switching, which opens a connection just long enough to send a small packet of data. Each packet includes a destination address informing the network where to send the packet along with the actual voice data payload. If the receiving station is also a VoIP terminal, then when the receiving terminal receives the packets, VoIP software executing on the receiving terminal reassembles the packets into the original data stream. The data stream is then converted to a voice signal. If the receiving station is a conventional telephone, then a VoIP gateway converts the packets into a voice signal that is then connected to the PSTN 1104.

In one embodiment, the VoIP process is performed using the H.323 standardized protocol established by the International Telecommunications Union (ITU). Advantageously, H.323 provides specifications for real-time, interactive videoconferencing, data sharing and audio applications such as IP telephony. Alternatively, the Session Initiation Protocol (SIP), established by the Internet Engineering Task Force (IETF), can be used. SIP is generally more efficient than the H.323 protocol as SIP is specifically intended for IP telephony. Alternatively, proprietary protocols could be deployed where multi-vendor interoperability is not required.

Optionally residing and executing on the computer terminal 1110 is a communications management Client application 1116. The Client application 1116 is used to provide enhanced communication services, as discussed in greater detail below. The Client application 1116 is connected to and communicates with the JAM system 1124 via the Internet 1106, other public wide area computer networks, or the like.

The JAM system 1124 optionally hosts a Web site used by subscribers of the JAM service to setup and manage their accounts, to view information about incoming calls, and to instruct the JAM system 1124 on how to route incoming calls to one or more destination stations. Many of these same functions can be implemented by the Client application 1116 as well.

The CM subsystem 1108 manages communications with the Client application 1116 and with forwarded calls. The CM subsystem 1108 can interact with callers and called parties through voice prompts, voice commands, and/or DTMF (dual tone multi frequency) touch-tone entries. The CM subsystem 1108 is optionally configured to perform additional functions, such as acting as a telephone answering system that answers calls, playing outgoing greetings and announcements, recording incoming messages, and bridging calls. In addition, as will be described in greater detail below, the CM subsystem 1108 further provides a call screening process.

The SM subsystem 1122 monitors the Internet for online IP devices registered to JAM subscribers to determine their availability for handling inbound call screening and call handling services. When a user or subscriber connects to the Internet using, for example, a dial-up ISP, the Client application 1116 executing on the subscriber's computer terminal 1110 makes the subscriber's online presence known to the JAM system 1124. Presence detection can be performed by the SM subsystem 1122 polling or pinging the computer terminal 1110 via the telecommunications Client application 1116, or by the telecommunications Client application 1116 transmitting a “Login/I'm alive” message and subsequent periodic “keep alive” messages to the SM subsystem 1122. Just prior to the normal termination of the online Internet session, the Client application 1116 sends a “Logout” message to the SM subsystem 1122. Abnormal Internet session termination conditions are detected by the SM subsystem 1122 timing out the expected Client “Keep alive” message.

If, rather than using a dial-up connection, the user or subscriber is using a broadband, always on-connection, such as via a DSL line or cable modem, the Client application 1116 becomes active when the computer 1110 is turned on or powered up and stays on until the user manually shuts down the Client application 1116, or the computer 1110 is turned off or powered down.

FIGS. 19A-19B illustrate one example embodiment of the present invention, including an abstraction of the previously described telecommunications system and an example call flow diagram. For clarity, the detailed breakout of the network elements and individual subsystems of the IAM system 1124 illustrated in FIGS. 16 and 17 are not shown in FIG. 19A. In this example, the calling party is associated with telephone terminal 1102 and the called party is associated with terminal 1112. In this embodiment, the called party is subscribed to an Internet call answering service that forwards calls to the remote IAM system 1124 upon the occurrence of selected conditions, wherein the IAM system 1124 transmits a notification to the called party regarding the call.

With reference to FIG. 16, the called party's station 1102 has been configured with the local switching system 1128 to forward calls on busy (BCF), ring-no-answer (RNA), or do-not-disturb (DND) to the voice trunk circuits 1118 connecting the CM subsystem 1108 to the PSTN 1104. The calling party initiates a call using the calling party telephone station 1102 by dialing the number of a called party's phone line 1114. The PSTN 1104 routes this call to the called party's local switching system 1128 causing the called party's telephone terminal 1112 to either ring or to forward the call immediately if the line 1114 is busy or set to do-not-disturb. If, for example, the called party does not answer within a certain amount of time or after a certain amount of rings, the associated switching system 1128 detects a no-answer condition and invokes a switch operation command termed “call forwarding on RNA”. The call is then forwarded to a phone number of the CM subsystem 1108.

Based at least in part on the OCN of the forwarded call (i.e. the original called party's phone number), the CM subsystem 1108 queries the SM subsystem 1122 to determine whether the called party is a registered subscriber, is online or offline, and what the subscriber's call handling preferences are. If the called party's computer 1110 is online, the CM subsystem 1108 opens a communication channel over the public Internet 1106 to the Client application 1116 running on the called party's computer terminal 1110. The Caller-ID of the calling party, if available, and if not designated as private, is transmitted to the Client application 1116 and is displayed to the subscriber along with an optional sound notification. The sound notification can be in the form of ringing produced using the called party's computer terminal 1110 speakers.

The CM subsystem 1108 proceeds to play a greeting to the calling party. The greeting can be a “canned” greeting or a personalized greeting previously recorded by the subscriber and stored in the MS subsystem 1138. The CM subsystem 1108 records and stores the caller's message in the MS subsystem 1138, while simultaneously “streaming” the message speech through the opened Internet channel to the Client application 1116 on the called party's computer terminal 1110. The Client application 1116 uses the computer terminal's codec to play the streamed speech through the speakers on the called party's computer terminal 110, thereby allowing the called party to listen to and screen the call. Optionally, to prevent the calling party from hearing any sounds made by the called party during the screening process, the audio return path over the Internet channel to the CM subsystem 1108 is muted.

While monitoring the Caller-ID of the incoming call, via the Incoming Call field illustrated in FIG. 18 for example, and listening to the corresponding streaming message, the called party is presented with one or more of the following options (see FIG. 18 which depicts an example Client application popup dialog menu):

-   -   1. do nothing.     -   2. pickup (answer) the call to talk to the caller using a         software telephone running on the “home PC” (the computer         terminal 1110).     -   3. pickup (answer) the call to talk to the caller using the         “home phone” on the phone line used to connect to the Internet         (the user telephone station 1112).     -   4. pickup (answer) the call to talk to the caller after         transferring the call to an alternate phone or to an alternate         PC.     -   5. continue screening the call after transferring it to an         alternate phone or to an alternate PC.     -   6. terminate the call substantially immediately—with a do not         disturb message.     -   7. do not answer the call.

The called party may choose to ignore the incoming call. For example, the call may not have been urgent enough to interrupt what they are doing or the call may have been intended for another member of the household. Under option (1), the called party can close the call handling options dialog box illustrated in FIG. 18 using the “CLOSE” option, thereby informing the JAM system 1124 that no further instructions for caller interaction will be forthcoming. Alternatively, the called party, having screened the Caller-ID of the incoming call and/or the associated caller's message, can simply continue doing what they were doing before the call arrived. After the caller has left a complete message, as indicated by the caller terminating the call or after a predetermined recording time period, the JAM system 1124 downloads the recorded message to the subscriber's computer terminal 1110 and updates the Client application's call log, which lists the calls handled by the JAM system 1124 for the called party. The message is archived in the MS subsystem 1138 and is also available locally on the computer terminal 1110 for playback at the called party's convenience.

Under option (2), the called party may decide to pickup the call in progress to talk to the calling party using the computer terminal 1110. Having screened the call, the called party can signal the JAM system 1124 to indicate a desire to talk to the calling party using VoIP. For example, the called party can activate the “HOME PC (VoIP)” option displayed in FIG. 18. After the called party has selected option (2), the Client application 1116 sends an instruction by way of an Internet-based client/server control message to the JAM system 1124. Upon receiving the instruction, the JAM system 1124 interrupts the recording and streaming process and plays a canned audio prompt to the calling party. The audio prompt can be, for example, “please hold while your call is being connected,” followed by audible ringing. The IAM system 1124 then bridges, in full duplex mode, the inbound call from the calling party to the CM subsystem 1108 with the outbound VoIP call from the CM subsystem 1108 to the called party computer 1110.

The JAM system 1124 will stay bridged between the calling party and called party for the duration of the call and may respond to internal events or called party actions. For example, the JAM system 1124 can selectively interrupt the bridged call if a time limit is exceeded and play an announcement to notify the calling party and/or the called party that the call will be terminated shortly. The IAM system 1124 can also initiate or transmit a warning message directly to the Client application 1116 that then displays a visual notice regarding call termination or the like on the called party's computer terminal 1110.

FIGS. 19A-19B illustrate an example call process workflow that can be used when a called party is online and can answer screened calls via a VoIP session. In this example, after screening the call, the called party agrees to talk directly to the caller. Of course, after screening the call the called party could have elected to decline the call. With reference to FIGS. 19A-19B, at state 1401, the calling party phone 1102 (hereinafter, referred to as the “calling party”) calls the called party phone line 1114 connected to the telephone 1112 and computer 1110. In this example, the computer 1110 is using the phone line 1114 to access the Internet; i.e. the computer is online and hence the phone line is busy.

At state 1402, the PSTN 1104 detects that the called party phone line 1114 is busy. At state 1403, in accordance with a call forwarding service, the PSTN 1104 forwards the call on busy to the JAM system 1124 via the voice trunk circuits 1118. At state 1404, the IAM system 1124 transmits an incoming call alert to the computer 1110 that is displayed to the called party by the Client application 1116. At the same time or shortly thereafter, at state 1405 the JAM system 1124 answers the forwarded incoming call. At state 1406, the PSTN 1104 establishes a full duplex, 2-way talk path with the calling party. At state 1407, the JAM system 1124 plays a greeting to the calling party. At state 1408, the calling party optionally begins leaving a voice message that is recorded by the IAM system 1124. Alternatively, similar to a telephone answering machine, the calling party can begin speaking to the called party even while the JAM system 1124 is playing the greeting. At state 1409 the JAM system 1124 begins streaming the message being left by the calling party in substantially real-time to the Client application 1116 or other media player executing on the computer 1110, which then plays the message to the called party.

At state 1410 of FIGS. 19A-19B, the IAM system 1124 generates a tone or other audio signal to indicate to the calling party that the calling party should begin recording a message. At state 1411, the calling party begins leaving a voice message. At state 1412, the IAM system 1124 begins streaming the message being left by the calling party in substantially real-time to the Client application 1116 or other media player executing on the computer 1110, which plays the message to the called party.

At state 1413, the called party notifies the IAM system 1124 that the called party wants to take the call. At state 1414, the IAM system 1124 interrupts the calling party, via a tone or voice notification. At state 1415, the IAM system 1124 requests that the calling party hold or wait while the IAM system 1124 connects the calling party to the called party. At state 1416, the IAM system 1124 bridges the calling party with the called party computer 1110, via the VoIP software module 1130, by establishing a VoIP session. This entails bridging the two calls together through the IAM system so that the caller and the called party can converse (state 1417):

-   -   the inbound call from the calling party 1102 connected into the         CM subsystem 1108 through the PSTN 1104; is bridged with     -   the outbound call from the CM subsystem 1108 connected through         the Router subsystem 1140 and the Internet 1106 to the VoIP         session running on the subscriber's computer terminal 1110.

Either party can terminate the call at state 1418 by hanging up their telephone (calling party station set 1102, or the called party can terminate the VoIP session on the computer terminal 110). At state 1419, the IAM system 1124 releases the bridging resources and signals completion of the call by sending a corresponding control message to the called party which is either displayed or played to the called party via the Client application 1116.

In another embodiment, the SM subsystem 1122 detects the presence of the called party on different IP devices, such as other computers or web-enabled cellular phones, at other locations. For example, the session manager SM subsystem 1122 optionally interfaces with other instant messaging services, such as:

AOL®'s Instant Messenger™

MSN®'s Instant Messenger™

Yahoo!® Messenger,

ICQ

where presence of the called party can be detected on other IP networks and at other geographic locations. The same call/session dialog described above is similarly performed in this embodiment.

Under option (3), the called party may decide to pickup the call in progress to talk to the calling party via a POTS telephone, such as the telephone terminal 1112. Having screened the call, the called party can signal the JAM system 1124 to indicate a desire to talk to the calling party. If the called party activates, by way of example, the “TALK @ HOME” key illustrated in FIG. 18 with the Home Phone radio button depressed, the Client application 1116 sends an instruction to the JAM system 1124 and then substantially immediately terminates the called party's dial-up Internet session in order to make available the called party's phone line 1114. Upon receiving the instruction from the Client application 1116, the JAM system 1124 interrupts the recording and streaming process and plays a canned voice prompt, such as “please hold while your call is being connected,” followed by audible ringing. The JAM system 1124 then proceeds to originate a new call on a free outbound voice trunk 1118 from the JAM system 1124 to the called party's phone line 1114. The call from the JAM system 1124 to the called party can be a local, intra-state, inter-state, or International PSTN call, as needed. Optionally, the call originated by the JAM system 1124 is to be jurisdictionally interstate so as to be rated and billed or charged as an interstate call. For example, in one embodiment, a six digit Information Element in the SS7 call setup message may be configured with the geographic area code and prefix of the Call Processing JAM System 1124 so as to cause the rating of the outgoing call to be Inter-state rather than Intra-state.

When the called party's phone line 1114 is answered a brief announcement is played to the called party and the JAM system 1124 then bridges, in full duplex mode, the inbound call between the calling party and IAM system 1124 with the outbound call between the IAM system 1124 and called party's line 1114.

In addition, the user can specify call handling rules that determine, at least in part, the call treatment for an incoming call based on one or more conditions. A rule can specify, for example, that if one or more conditions are met for a call, the call will be processing in accordance with a corresponding specified treatment. For example, the following conditions and automatic treatments can be defined:

Conditions:

-   -   Time-of-Day (can include a range of times), Day of Week (can         include a range of days), Day of Year (holiday)     -   Calling Party Number (Caller ID, non-local area code, phone         type, caller     -   name)     -   Called Party Number     -   Subscriber presence (IP device)     -   Telephony presence (phone)

Treatments:

-   -   Take a voice message (using selective greeting(s))     -   Take the call on home PC     -   Take the call on home phone     -   Take the call on work phone     -   Take the call on another phone     -   Remote screen on another phone(s) or other device(s)     -   Block call (for example, using an audio message, a SIT tone or         the like)     -   Do not answer call     -   Multiparty conference

By way of example, a subscriber can specify that if a call from a specified calling party number is received at a specified time of day (8:00-5:00), during the work week (Monday-Friday), the call should be forwarded to a specified phone, which can be the subscriber's work phone. By way of another example, a subscriber can specify that if a call to a specified phone number associated with the subscriber is received, on a holiday, remote screening should be performed using a different one of the subscriber's phone numbers.

If the call treatment specifies that the caller is to be connected to the subscriber using a given device, the subscriber can optionally still be provided with the ability to manually specify further call treatment, such as similarly described above. For example, the called party can be presented with one or more of the following options: take a voice message (using selective greeting(s)); take the call on home PC; take the call on home phone; take the call on office phone; take the call on another phone; remote screen on another phone(s) or other device(s); block call; do not answer call. Depending on the device the subscriber is currently using, the options can be provided via a visual menu, a voice menu, or the like.

FIGS. 20A-20B illustrate an example call process workflow that can be used when a called party requests to interrupt the caller message and to talk to the caller using the home telephone. With reference to FIGS. 20A-20B, at state 1501, the calling party calls the called party phone line 1114 connected to the telephone 1112 and computer 1110. In this example, the computer 1110 is using the phone line 1114 to access the Internet or other computer network, and so is online. At state 1502, the PSTN 1104 detects that the called party phone line 1114 is busy. At state 1503, in accordance with a call forwarding service, the PSTN 1104 forwards the call on busy to the IAM system 1124 via the voice trunk circuits 1118. At state 1504, the IAM system 1124 transmits an incoming call alert to the computer 1110 that is displayed to the called party by the Client application 1116. At the same time or shortly thereafter, at state 1505 the IAM system 1124 answers the forwarded incoming call. At state 1506, the PSTN 1104 establishes a full duplex, 2-way talk path with the calling party. At state 1507, the IAM system 1124 plays a greeting to the calling party. At state 1508, the calling party optionally begins leaving a voice message that is recorded by the IAM system 1124. Once again, the calling party can begin speaking to the called party even while the IAM system 1124 is playing the greeting. At state 1509 the IAM system 1124 begins streaming the message being left by the calling party in substantially real-time to the Client application 1116 or other media player executing on the computer 110, that then plays the message to the called party.

At state 1510 of FIGS. 20A-20B, the JAM system 1124 generates a tone or audible signal to indicate to the calling party that the calling party should begin recording a message. At state 1511, the calling party begins leaving a voice message. At state 1512, the IAM system 1124 begins streaming the message being left by the calling party in substantially real-time to the Client application 1116 or other media player executing on the computer 110, which plays the message to the called party.

At state 1513, the called party notifies the JAM system 1124 that the called party wants to take the call via the home telephone 112, and the IAM system 1124 instructs the Client application 1116 to terminate the online session of the computer 1110 by disconnecting from the Internet 1106. At state 1514, the IAM system 1124 interrupts the calling party, via a tone or voice prompt. At state 1515, the JAM system 1124 requests that the calling party hold or wait while the IAM system 1124 connects the calling party to the called party. At state 1516, the Client application 1116 terminates the online session of the computer 1110 by disconnecting from the Internet 1106 thereby idling the called party's telephone line 1114. At state 1517, the JAM system 1124 initiates a new call to the called party phone 1112. At state 1518, the called party answers the new incoming call from the JAM system 1124. At state 1519, the JAM system 1124 generates a call announcement to the called and/or calling party. At state 1520, the JAM system 1124 bridges the call between the calling party phone 1102 and the called party phone 1112. The calling and called parties can now conduct a normal telephone conversation at state 1521. Again, either party can terminate the call by simply hanging up their telephone (state 1522). At state 1523, the JAM system 1124 then releases the bridging resources and terminates the remaining call by optionally notifying the calling/called party that the other party has hung up and then disconnecting the call.

Under option (4), the called party may decide to pickup the call in progress to talk to the calling party using a communications device other than the telephone terminal 1112 or the computer 1110. Having screened the call, the called party signals the JAM system 1124 by, for example, activating the “TALK REMOTELY” button option illustrated in FIG. 18, to indicate a desire to talk to the calling party. As similarly discussed above with respect to option (3), based on the called party selecting option (4), the Client application 1116 sends a corresponding instruction to the JAM system 1124 along with a specification of the desired destination station phone number. The destination number specification can be an index into the subscriber's electronic phone book or may literally be the desired destination phone number. For example, the called party can select via the “Would you like to TALK to this caller” option that the called party wants to talk to the calling party using the called party's cell phone, office phone, other phone, or at a phone associated with a phone number entered by the called party in the “ENTER PHONE #” field.

Upon receiving the instruction from the Client application 1116, the JAM system 1124 interrupts the recording and streaming process and plays a voice prompt to the caller. The IAM system 1124 then proceeds to originate a new call on a free outbound voice trunk circuit 1118. In contrast to option (3) described above, the Client application 1116 does not terminate the online Internet session of the subscriber's computer terminal 1110. In fact, the Client application 1116 may continue online call monitoring operation while the above described transferred call is in progress. Multiple subsequent inbound calls could be simultaneously handled in this manner.

By way of example and not limitation, the destination station of the outbound call from the JAM system 1124 can include:

a wireless or cellular phone or device;

a called party's phone line and/or extension at work;

another POTS line of the called party (e.g. a second home phone number); or

a neighbor's or friend's phone line.

In addition, the called party can optionally specify the destination station by manually entering a phone number while the call is being screened. This new entry could be automatically journaled in an electric phone book available to the Client application 1116 or an extension to the options menu could popup to query the subscriber to determine if this is desired. Alternatively, the called party selecting an existing entry from the phone book can optionally dynamically assign the destination station. The phone book entries can be persistently stored locally on the computer terminal 110, in a centralized medium like the JAM DB subsystem 1136, or in both.

Under option (5), the called party may decide to allow the call in progress to be remotely screened using a communications device other than the telephone terminal 1112 or the computer 1110. This can optionally be in addition to continued screening of this call on the subscriber's computer 1110 or instead of continued screening of this call on the subscriber's computer 1110. The called party signals the JAM system 1124, using the “SCREEN REMOTELY” option illustrated in FIG. 18, to indicate a desire to remotely screen the incoming call. Once again, as similarly discussed with respect to options (3) and (4) above, based on the called party selecting option (5), the Client application 1116 sends a corresponding instruction to the JAM system 1124 along with a specification of the desired destination phone number. The destination number selection and specification is identical to that utilized in option (4) above, however the Screen Remotely options are used, rather than the Talk Remotely options. For example, the called party can select via the “Would you like to SCREEN to this caller” option that the called party wants to screen the calling party using the called party's cell phone, office phone, other phone, or at a phone associated with a phone number entered by the called party in the “ENTER PHONE #” field.

Upon receipt of this instruction, the JAM system 1124 initiates an outbound call from the CM subsystem to the specified destination phone number. The call setup signaling information for this outbound call is modified by the JAM system 1124 to deliver the calling party number from the inbound call in the outbound call's ANI field. This allows the forwarded destination station to display the “original Caller-ID” to use as a first level filter for remotely screening the call. Should the remote called party decide to ignore this call, they simply do not answer it and the JAM system 1124 will abort the transferred call attempt after a programmable time interval or a programmable number of ring cycles.

If the remote called party answers the transferred call, the JAM system 1124 plays a brief greeting prompt to the remote party to announce the remote screening call in progress. The caller message streaming can start at the beginning of the recording or cut over to live recording in real time. The output talk path from the remote party back to the JAM system 1124 is active but is muted with respect to the original calling party call. This allows the remote party to monitor the inbound call without the original calling party knowing that they are doing so. If the remote party decides to pickup the call in progress to talk to the calling party, they instruct the JAM system 1124 to bridge the two calls together by depressing a DTMF key or by uttering a voice command. Upon receiving this instruction, the JAM system 1124 interrupts the recording and streaming process and plays a canned audio prompt to the calling party. Once again, the audio prompt can be, for example, “please hold while your call is being connected,” followed by audible ringing. The JAM system 1124 then bridges, in full duplex mode, the inbound call from the calling party to the CM subsystem 1108 with the outbound call from the CM subsystem 1108 to the remote called party station.

Once again, the JAM system 1124 will stay bridged between the calling party and remote called party for the duration of the call and may respond to internal events or called party actions. For example, the JAM system 1124 can selectively interrupt the bridged call if a time limit is exceeded and play an announcement to notify the calling party and/or the remote called party that the call will be terminated shortly. The JAM system 1124 can also transmit a warning message (such as a short text message) over the Internet 1106 to the remote station set that then displays a visual notice regarding call termination or the like.

Under option (6), the called party may decide to not accept calls from the calling party. Having screened the call, the called party can signal the JAM system 1124 to abort the caller's message recording and to communicate the request to not be called in the future. For example, the called party can activate the “BLOCK CALL” option illustrated in FIG. 18. The called party can either select a do not answer option or a “Tell them to TAKE ME OFF their list” option. As in the cases above, based on a user action the Client application 1116 sends a corresponding instruction to the JAM system 1124. Upon receiving the “Tell them to TAKE ME OFF their list” instruction from the Client application 1116, the JAM system 1124 interrupts the recording and streaming process, plays a voice prompt to the caller, such as: “The person you have called does not accept solicitations, please remove this phone number from your calling list. Thank you and goodbye.” The JAM system 1124 then disconnects the call. The options dialog box could pop an additional query to determine if the subscriber would like the JAM system 1124 to always apply this treatment to future calls from this Calling phone number. This automatic call handling rule would be stored in a table of subscriber preference settings local to the IAM system 1124 (for example in a simple extension table of the subscriber's phone book). If directed to do so, the IAM system 1124 would automatically screen-out future calls from this caller and not “bother” the subscriber with needing to handle them.

Option (7) is a variant of option (6). The called party can monitor the Caller-ID of the incoming call and decide to not accept calls from this calling party. The IAM system 1124 could be optionally configured to delay answering the incoming call for a fixed time interval or for a specific number of ring cycles in order to allow the subscriber time to review the Caller-ID. If the Client application 1116 instructs the IAM system 1124 to block the call in this manner before the incoming call has been answered, the IAM system 1124 will ignore the call (i.e. let it ring). If the Client application 1116 instruction comes after the incoming call has been answered, the IAM system 1124 will apply the call treatment described above for option (6). Alternatively, the IAM system 1124 could be configured to instead default to a standard Internet answering call when the Client application 1116 instruction comes after the incoming call has already been answered. Once again, the options dialog box could pop an additional query to determine if the subscriber would like the IAM system 1124 to always apply this treatment to future calls from this Calling phone number. Again, these automatic call handling rules would be stored in the IAM system 1124 and, when directed to do so, the IAM system 1124 would automatically screen-out future calls from this caller and not “bother” the subscriber with needing to handle them.

The above scenarios describe situations in which the called party's computer 1110 is on-line and serves as the initial IAM call screening device. Alternatively, the IAM system 1124 could be configured to automatically forward the call notification announcement and streamed caller message to an alternate device such as a POTS or wireless telephone or another online IP device. This alternative call screening device selection could be configured to vary based on the availability of the online presence of the called party's computer 1110 or alternate IP devices, on the Caller-ID of the calling party 1102, on the dialed number for the Called party 112, on the reason that the call was directed to the IAM system 1124 (for example, call forwarding on busy, ring-no-answer, or do-not-disturb conditions), on time of day, day of week, etc. Configuration rules governing the automatic call handling treatment can be stored in the JAM DB subsystem 1136.

The following process describes a typical JAM call screening scenario when the called party's computer 1110 is offline. When the called number forwards on busy, ring-no-answer, or do-not-disturb, and arrives on one of the JAM voice trunks 1118 along with the signaling information, the CM subsystem queries the SM subsystem 1122 and/or the JAM DB subsystem 1136 using the incoming call's OCN (the original called party number) to determine that the call is for a registered subscriber, to determine the subscriber's online/offline presence status, and to retrieve that subscriber's call handling preference rules. Assuming that the subscriber has previously configured the account to handle diverted offline calls, the JAM system carries out the specified call handling treatment. This could be simply to answer the call and take a message. Alternatively, it could include one of the seven call management options previously described. For example, the subscriber may have specified that automatic remote call screening on their cell phone was desired when their home computer 1110 was not online. In this case, the CM subsystem 1108 originates another call to the destination device, based on the previously described configuration rules. Additionally, the CM subsystem 1108 may optionally delay answering the incoming calling party's call for a predetermined amount of time or number of rings. This gives the called party additional time to answer the call originated from the CM subsystem 1108.

Normally, when the JAM system 1124 originates a call, the calling party ID passed in the SS7 and/or ISDN-PRI trunk signaling is the calling party ID of the trunks originating the call. In one embodiment, the CM subsystem 1108 modifies the network signaling to replace the calling party ID of the trunks to be that of the phone number of the original calling party. Thus, a Caller-ID device will advantageously display the phone number of the original calling party. The call is processed in an analogous above described fashion for handling a remote screening call forwarded by the subscriber from the online computer 1110 to a wireless station. If the called party answers the call, the JAM system 1124 plays a brief announcement of the call to the subscriber and the inbound call is answered by the JAM system 1124 (if not already answered due to timeout reasons). For example, the CM subsystem 1108 might announce the call as “This is an Internet Answering Machine call for John Doe”. The IAM system 1124 then bridges the inbound calling party call with the outbound called party call. The IAM system 1124 optionally mutes the return talk path to prevent sound traveling back to the calling party so that the calling party is unaware that their call is being screened. Preferably, though not required, the called party is bridged onto the call as the called party is either listening to a personal/system greeting or, as the calling party is beginning to leave a message for the called party. In this manner, the called party can further screen the call.

Once the called party begins to screen the call, the called party may decide not to connect to the calling party. The called party, having screened the caller who is in the process of leaving a message, can hang up, thereby terminating the bridged call without the calling party being aware that the screening process took place. The calling party can continue to leave a message for the called party after the bridged call is terminated. Alternatively, the called party may decide to pickup the incoming call to talk to the calling party. Having screened the calling party, the called party can signal the CM subsystem 1108, by entering a touch-tone signal or providing a voice command, to indicate a desire to talk to the calling party. The IAM system 1124 will then bridge in full duplex mode the call between the calling party and CM subsystem 1108 with the call between the CM subsystem 1108 and called party.

The IAM system 1124 will stay bridged between the calling party and called party. The IAM system 1124 can selectively interrupt the bridged call if a predetermined time limit is reached and play an announcement to the calling and/or the called party that the call will be terminated shortly. Optionally, this announcement will only be played to the called party. In another case, the IAM system 1124 can selectively interrupt the bridged calls to announce to the called party that the call will be terminating unless the called party authorizes billing by entering a touch-tone command or by providing a verbal authorization to charge the called party's telephone number or a credit card.

In another embodiment, an external bridging system (hardware and/or software), including a connecting switch, is used to bridge calls. The CM subsystem 1108 can instruct the connecting switch located within the PSTN 1104 equipped with the call bridging system to create a 3-party conference call between the calling party, the called party, and the JAM system. This process advantageously reduces the number of voice ports needed on the JAM system 1124. In this scenario, the called party can optionally signal the switch with touch-tone or voice commands to cause the JAM system 1124 to connect back into the bridged call.

The example embodiments described above referred to calls forwarded from a called party's line. Another embodiment uses a personal number uniquely assigned to each subscriber by which calls to that number can be screened. The personal number can be, for example a telephone number that has been acquired through governmental telephone number administration bodies, provisioned in the PSTN network, assigned to the JAM system 1124 and registered to an individual subscriber.

The personal number call screening process will now be described. A calling party 1102 at a phone dials a phone number published by a subscriber to the JAM system 1124. The call routes through the PSTN 1104 and terminates on the JAM voice trunk 1118 along with its associated call signaling information. Thus, for example, rather than using an existing wireless or POTs phone number, a subscriber can publish a private phone number, wherein all calls to the private phone number undergo an automatic screening process, as previously described. This technique enables the subscriber to better manage their incoming call costs.

Using the called party personal phone number or normal phone number as a search key or index, the JAM system 1124 extracts or retrieves call treatment actions and conditions stored in association with the called party personal number or normal phone number. The call treatment conditions and actions can include some or all of those described above. For example, the conditions can include one or more of:

-   -   Time-of-Day (can include a range of times), Day of Week (can         include a range of days), Day of Year (holiday)     -   Calling Party Number (Caller ID, non-local area code, phone         type, caller     -   name)     -   Called Party Number     -   Subscriber presence (IP device)     -   Telephony presence (phone)

The call treatments can include one or more of:

-   -   Take a voice message (using selective greeting(s))     -   Take the call on computer     -   Take the call on POTS phone (specify home, work, other POTS         phone)     -   Take the call on a wireless phone     -   Remote screen on another phone(s) or other device(s)     -   Block call (for example, using an audio message, a SIT tone or         the like)     -   Do not answer call     -   Multiparty conference

The following is a more detailed description of example call treatment actions that can be executed or orchestrated by the IAM system 1124:

-   -   Do not answer action: the incoming calling party phone number is         screened against a list of phone numbers or subscriber-specified         other criteria (such as no caller id available), wherein if the         calling phone number matches the listed phone numbers and/or the         other criteria, the incoming call is not answered;     -   Take call on computer (online/offline status action): if the         called party is online when a call is received, initiate a VoIP         session with the Client application 1116 running on the         subscriber's IP device 1110 and screen the call as described         above;     -   Take the call on POTS phone action: originate a call to a         specified POTS line and bridge the POTS call with remote         screening as described above;     -   Take the call on POTS phone action: originate a call to a         wireless phone action and bridge the wireless call with remote         screening as described above; or     -   multi-party conference action: in which the call screening         session described above is broadcast to multiple phones and IP         Clients substantially at the same time.

In one embodiment, the multi-party conference action can include the following states. A first call processing apparatus, such as the IAM system 1124, receives a call from a first user for a second user. A voice communication from the first user is received at the first call processing apparatus. At least a portion of the voice communication is multicasted to a plurality of client devices, which can include for example POTs, wireless, cellular and/or VoIP phone devices, at substantially the same time so that the first user's call can be screened. An instruction is received via a first of the plurality of client devices to connect the first user to a first of the plurality of client devices. The second user is then bridged to the first of the plurality of client devices.

In another embodiment, the multi-party conference action can include the following states. A first call processing apparatus, such as the IAM system 1124, receives a call from a first user for a second user. A call alert is then multicasted to a plurality of client devices, which can include for example POTs, wireless, cellular and/or VoIP phone devices, at substantially the same time so that the first user's call can be screened. In addition, a voice communication received from the first user can be multicasted to the plurality of client devices at substantially the same time. The call alert can include at least a portion of Caller ID information associated with the first call. An instruction can then be received via a first of the plurality of client devices to connect the first user to a first of the plurality of client devices. The second user's call is then bridged to the first of the plurality of client devices.

Still another embodiment of a call transfer process will now be described. By way of example, a call can be received from a caller for a called party at the call processing system, such as, by way of example, the call processing system 1124. The call may have been placed by the caller to a virtual telephone line or a number associated with the called party, wherein when a call is placed to that number, the call is connected to the call processing system. The call may also have been placed to a phone associated with the called party, and the call may have been forwarded as a result of a call forwarding on busy, a call forwarding on ring-no-answer, or a call-forward-all calls (sometimes called do-not-disturb) condition. Upon receiving the call, the call processing system can automatically transfer or connect the call, via a call bridging operation or otherwise, to a first target phone, such as a wireless, VoIP, or landline POTS phone, associated with the called party. The transfer can optionally be initiated based at least in part on a prior instruction from the called party stored in computer readable memory, such as in an account database record.

In addition, a caller identifier can optionally be provided to the called party via the first phone. For example, as similarly described above, if the first phone is a wireless phone, POTs phone, or other phone capable of displaying Caller ID information, the caller identification can be provided via the ANI field as a phone number to be presented on a display associated with the phone. The called party can optionally use the identification information to screen the call.

To further allow the called party to screen the call, the call processing system can play a greeting to the caller and ask the caller to leave a message. The call processing system can play a greeting prompt to the called party to announce the remote screening call in progress. The caller message can be streamed to the called party's first phone. Optionally, the output talk path from the remote called party back to the call processing system is active but the output talk path is muted with respect to the original calling party call. This allows the called party to monitor the inbound call without the calling party knowing that they are doing so.

In addition, the called party can, via a phone key press, voice commands, or otherwise, instruct the call processing system to accept the call or to forward or bridge the caller's call to another target/second phone, such as a POTs phone, a wireless phone, a VoIP phone, a networked computer, or other communication device. Optionally, the called party can specify whether the call is to be transferred with supervision, wherein the call processing system will maintain the outcall to the first phone until the new target phone is answered, or without supervision, wherein the outcall to the first phone is terminated even before the new target phone is answered.

Further, the called party can specify whether the call should be transferred with call screening or without call screening. Optionally, the called party can set defaults with respect to supervision and call screening, wherein the default can be stored on the call processing system or in other computer readable memory. For example, the called party can set the defaults by configuring the called party's account. Then, further manual and/or auto-transfer call processes can be performed in conformance with the supervision and/or call screening defaults.

An example call transfer process will now be described. After receiving a call intended for a called party, the call processing system can place an outcall to a telephone associated with the called party, and can play a message or prompt to the called party, instructing the caller as follows: “You have a call, press the 1 button to accept the call (on the current telephone), the 2 button to have the call connected to your home phone without screening, the 3 button to have the call connected to your home phone with screening, the 4 button to have the call connected to your work phone without screening, the 5 button to have the call connected to your work phone with screening, the 6 button to connect the call to your VoIP phone without screening, the 7 button to connect the call to your VoIP phone with screening, the 8 button to have the call processing system record a message from the caller, the 9 button to have a message played by the call processing system to the caller informing the caller that you refuse to take the call, or the * button to disable further auto-transfer calls.”

The prompt can optionally include speaking the phone numbers associated with the destination (for example, “press the 2 button to have the call connected to your home phone 5555 555-5555”). Several different prompts can optionally be stored by the call processing system, and selectively provided. For example, if the initial outcall is to the user's home phone, then the home phone options (“press . . . the 2 button to have the call connected to your home phone without screening, the 3 button to have the call connected to your home phone with screening”) can optionally be omitted.

In this example, the called party can press the “1” button to accept the call, the “2” button to have the call connected to the home phone without screening, the “3” button to have the call connected to the home phone with screening, the “4” button to have the call connected to the work phone without screening, the “5” button to have the call connected to the work phone with screening, the “6” button to connect the call to the VoIP phone without screening, the “7” button to connect the call to the VoIP phone with screening, the “8” button to have the call processing system record a message from the caller, or the “9” button to have a message played to the caller informing the caller that the called party refuses to take the call. Optionally, the called party can prevent or disable future auto-transfer calls by pressing an appropriate button, such as the “*” button. If the called party gave a call transfer instruction (such as by pressing the 3, 4, 5, 6, or 7 button in this example), in response to receiving the called party instruction, the call processing system can retrieve the corresponding phone number from the user account database record or elsewhere, stored in computer readable memory, and transfer the call to the retrieved phone number.

The called party can similarly be instructed to press one or more buttons in order to have the call transferred with or without call screening.

Thus, optionally, the user does not have to key in or remember the phone number the user wants the call to be transferred to each time a call comes in. In addition, in this example embodiment, the initial target phone does not have to be set up or programmed with the call transfer phone numbers, and so the user can use a wide variety of phone terminals, such a hotel phones, work phones, and so on, to receive calls and to instruct the call processing system to forward the calls to another destination.

The term key or button press, as used herein, can include the pressing of a physical key or button, a soft key or button displayed on a touch sensitive or other display, a corresponding spoken number or command, or other form of instruction.

Optionally, the called party can provide the instruction to connect the call to another phone before initiating the conversation with the caller, such as while screening the call, or during the conversation with the caller, such as after accepting the initial call bridged to the called party by the call processing system.

Optionally, the called party or other user can access the call via the target phone and instruct the call processing system, via a key press, such as a single key press or two or more key presses, voice instruction, or otherwise, to transfer or connect the call, via a call bridging operation or otherwise, to still another communication device.

Optionally, in order to insulate the called party to the foregoing process, the calling party can be prevented from hearing all or a part of the called party's key press(es) or voice instruction(s). For example, the call processing system can tear down or mute the audio path from the target phone to the caller's phone. If the call has been transferred and the called party wants to transfer to another line, the detection of a called party key press can be performed very quickly, such as in 10 ms or less, to reduce or minimize the audible transmission of the DTMF tone resulting from the key press to the caller.

Thus, by way of example, if a called party receives the forwarded, bridged, or otherwise transferred call on the called party's wireless phone or other target phone, in order to reduce the amount of wireless time or minutes used, to save battery power, to avoid the call being dropped due to a low battery charge, and/or to communicate via a medium that provides better voice quality, the called party can have the call further forwarded, bridged or otherwise transferred to a POTs phone, wireless cellular phone, VoIP phone, or other communication device.

By way of further example, a call can be received from a caller for a called party at the call processing system. The call processing system can automatically transfer or connect the call, via a call bridging operation or otherwise, to a wireless, POTs, networked computer, or VoIP phone associated with the called party. The transfer can optionally be initiated based at least in part on a prior instruction from the called party.

In addition, a caller identifier can optionally be provided to the called party via the target phone. For example, as similarly described above, the caller identification can be provided via the ANI field as a phone number to be presented on a display, such as a Caller ID display, associated with the target phone. The called party can optionally use the identification information to screen the call. In addition, the called party can, via a phone key press, voice commands, or otherwise, instruct the call processing system to forward or bridge the caller's call to another target phone, such as a another POTs phone, a wireless phone, a VoIP phone, or other communication device. For example, the call processing system can provide prompts similar to those described above or otherwise, and the called party can provide corresponding responses. By way of example, the call processing system can provide the following prompt: “You have a call, press the 1 button to accept the call (on the current telephone), the 2 button to have the call connected to your home phone without screening, the 3 button to have the call connected to your home phone with screening, the 4 button to have the call connected to your work phone without screening, the 5 button to have the call connected to your work phone with screening, the 6 button to connect the call to your VoIP phone without screening, the 7 button to connect the call to your VoIP phone with screening, the 8 button to have the call processing system record a message from the caller, or the 9 button to have a message played by the call processing system to the caller informing the caller that you refuse to take the call.”

If the call is transferred to second target phone or line, some or all of the same call transfer and processing options can be offered again to the called party once the call is transferred to the second phone, or still other options can be offered.

Optionally, a user can specify the auto-transfer number via one or more user interfaces provided by or coupled to the call processing system. For example, the user interface can be provided via the IAM client, such as that discussed above, executing on the user's computer terminal, via an IAM client executing on a smart phone, such as a smart phone using a Microsoft, Symbian, or Palm operating system, via a TUI (telephone user interface) that can provide voice or other prompts over the phone and via which the user can provide instructions via telephone key presses and/or voice commands, or otherwise. For example, if the user is on travel, the user can set the auto-transfer number via the TUI or otherwise to a phone number/line associated with the hotel where the user is staying.

If the user is setting the auto-transfer number via a telephone/telephone line that provides the phone number associated with the calling line, such as via Caller ID, or otherwise provides caller identification signaling information, upon receiving the call set-up information, the call processing system can use such signaling information to automatically authenticate the user and to access the user's account information. The user can optionally also be prompted to enter a password to further provide authentication. Once the authentication is performed, the user can be allowed to specify a new auto-transfer phone number.

Optionally, for broadcast purposes, the user can specify that incoming calls are to be auto-transferred to a plurality of different phones, including one or more POTs phone, wireless phone, VoIP phones, and/or other target phone devices. The auto-transfer can include call screening as described above. Thus, an incoming call can be screened by a plurality of users using a plurality of the corresponding target phone devices. A user can then elect to accept or further transfer the call to a second target phone or line with or without screening and with or without supervision, as similarly described above. Then, for example, the called party or other user can access the call via the second target phone and instruct the call processing system, via a key press, voice instruction, or otherwise, to transfer or connect the call, via a call bridging operation or otherwise, to a third communication device, and so on.

Thus, by way of example, if a called party receives the forwarded, transferred or bridged call via the call processing system on the called party's home POTs or other landline phone as the called party is about to leave home, or otherwise lose access to the landline POTs phone, the called party can elect to manually transfer the call to the called party's wireless, mobile cell phone in order to continue the conversation with the caller after leaving home.

By way of further example, if the called party instructs the call processing system to connect the incoming call to a designated communication line, the call processing system can initiate an outcall to the designated communication line. While the outcall is “ringing”, optionally, a ringing tone or a waiting tone can be played to the caller. Optionally, if the user instruction to transfer the call occurred during the call, wherein the caller and called party were conducting a conversation, the caller and called party can continue the conversation on the original phone line until the call on the target line is answered.

Optionally, if the outcall is not answered after a certain predetermined time period (such as after a number of seconds), after a certain number of rings, or if the new target line is busy, the outcall can be terminated, and a call transfer failed message, tone, or other indicator can be played or provided to the called party and/or the caller. If the outcall is answered, the outcall and the caller's can be bridged or otherwise connected. Optionally, a message, tone, or other indicator can be provided or played on the caller's phone, the original called party's phone, and/or the new, target phone, notifying the caller and/or the called party that the call has been transferred. The connected between the call processing system and the original called party phone can be dropped.

Optionally, the foregoing call transfer process may only be offered to the called party if the called party has designated an alternate phone number/line and/or is authorized or has permission to utilize the call transfer process. If the called party has not specified an alternate number/line designator (wherein the phrase “number” includes an address for a VoIP terminal or other communication designator) and/or does not have authorization to use the call transfer call process, optionally an instruction, such as in the form of a key press, from the called party to utilize the call transfer process can be ignored, or a message can be played to the called party notifying that the called party has not provided an alternate number and/or does not have authorization to use the transfer process.

An embodiment of a call transfer process will now be discussed in greater detail with reference to FIG. 21, wherein a call is automatically transferred to a first destination associated with a called party, who can optionally then cause the call to be transferred to still another destination. The components illustrated in FIG. 21 can optionally correspond to components of the same name or type discussed above with reference to FIGS. 16-20. As with the other processes and corresponding figures described herein, not all states need to be reached, and the states do not necessarily need to be performed in the same order as that illustrated. In addition, certain state processes do not need to be performed serially, and two or more states processes can be performed in parallel. The processes can include additional states as well. While the following example assumes that the auto-transfer destination is a wireless, cellular phone, the destination can be a POTs phone, a VoIP terminal, or other destination or communication device.

State 1. An incoming call (incall) intended for a subscriber or other user is presented to a call processing system, such as that previously described.

State 2. The call processing system receives subscriber information, such as from the Session Manager by way of example, which can retrieve the subscriber information from a subscriber database. The subscriber information can include a target destination, such as a phone number/line identifier (such as a VoIP line identifier) to which calls are to be automatically transferred.

State 3. The call processing system optionally transmits a call notification/message to the subscriber/user IAM client and places an outgoing call (outcall) to the auto transfer destination. The user can use either the IAM client or the auto-transfer destination terminal to accept the call or to further transfer the call as discussed below. State 3 can performed in parallel with state 4.

State 4. If, for example, the auto transfer destination is a wireless cell phone, one or more of the following next processes can occur.

-   -   (a) the outcall can be answered at the called party/customer         wireless phone;     -   (b) the called party notifies on instructs the call processing         IAM system that the called party wants to take the call via the         IAM client or otherwise. The call processing IAM system bridges         the calling party with the called party computer hosting the IAM         client, by establishing a VoIP session via a VoIP software         module. The two calls are bridged together through the by         establishing a VoIP session IAM system so that the caller and         the called party can converse;     -   (c) an outcall timer expires, wherein if the called party does         not answer the call or does not otherwise take the call, the         outcall is dropped.

State 15. The call processing system answers the incall.

State 6. If the outcall was successfully connected to the wireless cell phone (or other destination telephone or terminal), the called party can press a key to generate a tone, such as DTMF 2, to transfer the call to their home. Once the IAM system receives the tone, the Session manager can retrieve the corresponding transfer destination, such as a home phone number, from the subscriber database. A short confirmation prompt can be played by the call processing system to the called party if the outcall is queued. If the outcall is not queued, as might occur if there are no available ports, an explanation of why the outcall could not be queued can be provided, and the called party can accept the call on the wireless cell phone by pressing the appropriate button, such as a ‘1”. After the prompt, the called party returns to screening or talking to the caller. (Note: the called party could also optionally take the call on their cell phone immediately by pressing “1”.)

State 7. If the outcall was successfully queued, an outcall is placed from the call processing system to the home or other designated destination.

State 8. The outcall to the home phone number, or other destination, is answered. This outcall is optionally immediately connected and the caller can then talk to the called party, where the called party can talk from the home phone.

State 9. If the call transfer was performed with supervision, a message is optionally played by the call processing system to the called party via the called party's cell phone, where the message informs the called party that the call has been connected to the home phone line, or other designated destination, and then the call between the call processing and the wireless cell phone is hung up or otherwise disconnected. If the call transfer is unsupervised call, the call between the call processing and the wireless cell phone is dropped at state 7.

State 10. The called party can optionally forward the call back to their cell phone, or to another phone/phone line during the call with the called party by pressing an appropriate phone key, such as the “2” key.

A description of example embodiments of making the auto-transfer process available, of calculating an outcall duration (the time after bridged call is originated by call manager), of presenting the call transfer process to the caller and the called party, and of maintaining call processing records will now be provided.

Optionally, the auto-transfer process is configured for individual subscribers or other users via one or more of the following “class of service” controls stored in the subscriber or other user database. For example, a user/subscriber can selectively enable or disable the auto-transfer process via a user accessible web page which can be hosted by the IAM system. By way of further example, the user/subscriber can also enable or disable the ability to use the web page to enable or disable the auto-transfer process. The user/subscriber can also selectively enable the auto-transfer process for calls placed while the user/subscriber is online and connected to the call processing IAM system via an IAM client. The user/subscriber can also selectively enable the auto-transfer process for calls placed while the user/subscriber is not connected to the call processing IAM system via the IAM client. Similar controls are provided for calls placed to the user/subscriber virtual telephone line or a number without a physical line tied to it. The user can also optionally specify a call duration. Further, the user/subscriber can selectively specify that only calls that have Caller ID information available should be auto-transferred, or can specify that even calls without Caller ID information available should be auto-transferred.

Optionally, the user and/or the system operator can specify a time period and/or number of rings before an auto-transfer incall is answered by the call processing system and a caller message is taken. Different time period can optionally be specified for different users/subscribers. For example, a new user can be provided a shorter incall answer time period, such as 15 seconds, than the time period, such as 25 seconds, for a user with a premium service, such as might be provided upon payment of an appropriate one time and/on periodic fee. Optionally, the user and/or the system operator can specify a time period and/or number of rings before an auto-transfer outcall is abandoned by the call processing system, wherein different time periods can be specified for different users/subscribers as similarly described for the incall.

In addition, the amount of guidance or help provided to a user/subscriber with respect to the auto-transfer process can be specified, as well as whether screening should be provided, and/or whether the auto-connect process is to be provided. By way of example, the user and/or system operator can specify that a phone number associated with the call processing system should be used as the caller ID for the IAM system outcall.

An example table is provided below listing example auto-transfer controls, one or more of which can be provided by the call processing system. The table lists example control names and descriptions. Optionally, there can be associated default values. Different users and/or different class or sets of users can be assigned different default values. The user can set the values/states via a Web page, a TUI interface, or otherwise. With reference to the table below, CVL is a voice line, such as a virtual telephone line or a number without a physical line tied to it. For example, the user can designate which terminal/line calls to the CVL number will be connected to. By way of illustration, the user can specify that calls to the CVL number as such be connected to a voice mail system, a cell phone, a home phone, a work phone, or other telephone/line. The user can optionally change the destination via a call processing system account manager. The corresponding values can be stored in a database accessible by the call processing system Call Manager or other call processing system.

TABLE 1 Auto-Transfer Controls Control Name Description FwdAutoTransferAllowed Specifies whether the subscriber has the auto- transfer feature for calls to a subscriber's target or forwarded number. FwdAutoTransferOnlineEnabled Specifies whether auto- transfer is enabled for calls to a subscriber's target or forwarded number when the subscriber is online (connected to the call processing IAM system via the IAM client). FwdAutoTransferOfflineEnabled Specifies whether auto-transfer is enabled for calls to a subscriber's target or forwarded number when the subscriber is offline. (not connected to the call processing IAM system via the IAM client). CVLAutoTransferAllowed Specifies whether the subscriber has the auto- transfer feature for calls to a subscriber's CVL Number. CVLAutoTransferOnlineEnabled Specifies whether auto- transfer is enabled for calls to a subscriber's CVL Number when the subscriber is online. CVLAutoTransferOfflineEnabled Specifies whether auto-transfer is enabled for calls to a subscriber's CVL Number when the subscriber is offline. ConnectDuration Used to determine the duration of the connected call, as described in greater detail below. AutoTransferCallerIdRequiredEnabled Specifies whether the auto- transfer should only occur if the caller ID (or other caller identifier) is available. AutoTransferIncallRingTimerSeconds Specifies the number of seconds (or other time unit) before an auto-transfer incall is answered by the call processing system, a greeting is played, and a message is taken. The called party can screen the caller message and decide to accept the call. Optionally, this setting is not exposed to the subscriber. This parameter can be configured by the system operation, and the subscriber can selectively be allowed or not allowed to conFIG.the incall ring time. AutoTransferOutcallRingTimerSeconds Specifies the number of seconds, or other time unit, to ring an outcall before it is abandoned. Optionally, this setting is not exposed to the subscriber. This parameter can be configured by the system operation, and the subscriber can selectively be allowed or not allowed to conFIG.the incall ring time. AutoTransferPresentationStyle Specifies the subscriber's experience when answering an auto-transfer outcall. For example, a Tutorial with Screening, Screening, or Auto Connect mode can be specified. AutoTransferUseMrtCallerId Specifies the phone number to be used as the Caller ID or ANI for the outcall.

In addition, the user can specify an auto-transfer phone number (AutoTransferPhoneNumber) which is stored in a corresponding database field. The AutoTransferPhoneNumber is the phone number to which auto-transferred calls for the subscriber are to be transferred. Optionally, the value of the field can be empty or null until specified by the user/subscriber.

With respect to the connect outcall timing, optionally a connect outcall (including auto-transfer and/or manual outcalls) has a maximum call duration set and an associated warning type. The maximum call duration specifies how long the call is allowed to be connected before the call processing system terminates the call. Optionally, a maximum call duration of zero (or other designated value) indicates that the call is not disconnected by the call manager system unless the processing system, or a selection portion thereof is shut down.

The warning type specifies how long before the end of the outcall (as specified by the connect outcall timing) the subscriber receives a first and a second warning (or still additional warnings), and what prompts are used for these warnings. The following table describes example warning types, although other warning types and other timings can be used as well. In addition, the call processing system can optionally automatically provide warnings that announce an expiration time that is shorter that the actual expiration time to take into account users whose perception of time is incorrect:

TABLE 2 Outcall Duration by call type First Warning Second Warning Warning Timing Timing Type (seconds) Prompt (seconds) Prompt Short 120 “You have two 45 “You have thirty minutes left” seconds left”(*) Long 180 “You have three 45 “You have thirty minutes left” seconds left”(*)

Optionally, the maximum outcall duration and warning type for a call are determined by the call processing system by finding a row in a database table that matches the subscriber's connectDuration, incall type (such as Forwarded, CVL No. 1, CVL No. 2), and the transfer type (such as auto-transfer or manual transfer). Associated call durations and warning types (short or long) can be provided in the table as well. The following table illustrates example values of the database table. Different users can be entitled to different classes of services. For example, some users can be associated with a Class 1 level of services, while other users can be associated with a Class 2 level of services, wherein Class 1 can offer a higher level of services than Class 2 in one or more categories.

TABLE 3 Outcall Duration by call type Maximum Call Connect Incall Transfer Duration Warning Duration Type Type (Minutes) Type 1 Forwarded Auto 60 Long (used by a Manual 60 Long relatively CVL No. 1 Auto 60 Long high class of Manual 60 Long service ) CVL No. 2 Auto 60 Long Manual 60 Long 2 Forwarded Auto 30 Short Manual 30 Short CVL No. 1 Auto 30 Short Manual 30 Short CVL No. 2 Auto 30 Short Manual 30 Short 3 Forwarded Auto 10 Short (used by the Manual 10 Short low class of CVL No. 1 Auto 10 Short service ) Manual 10 Short CVL No. 2 Auto 10 Short Manual 10 Short

Optionally, the call duration can be based at least in part on a toll level on the outcall. For example, calls placed to SIP (Session Initiation Protocol) devices could be allowed to continue without a limited duration or for an extended duration, such as 2 or 4 hours. Optionally, the outcall duration table data can be cached in solid state memory, and can be periodically refreshed.

If an outcall duration database row cannot be found that matches the subscriber's connectDuration, incall type, and the transfer type, optionally an exception is logged and default connect duration (defaultConnectDurationMinutes) and default warning type (defaultWarningType) parameter settings are read from memory, such as a timing cache (OutcallTimingCache), wherein the foregoing parameters are described in the configuration description below.

A connectDuration of zero is allowed. Optionally, calls for subscribers that have a connectDuration of zero will have the default behavior described above applied.

Example configuration parameters will now be discussed. Fewer or additional configuration parameters can be used. A given call processing system Call Manager can have one or more of the following dynamic configuration parameters that control the use and application of the Auto-Transfer feature. The default values described below are examples, and other default values can be used as well. Certain example time units are used, such as seconds or minutes, however other time units can be used as well:

-   -   [OutcallTimingCache] secondsBetweenSync—How often the table         storing the connect call duration by call type information is         refreshed in seconds or other units.     -   [PortManager] shutdownFirstWarningDelaySeconds—How long between         when a Call Manager, or other designated call processing system         subsystem, shutdown is requested and the first shutdown warning         to subscribers on out-calls.     -   [PortManager] shutdownSecondWarningDelaySeconds—How long between         the first warning and the second warning (for out-calls) when         the Call Manager is shutting down. By way of example, the value         can have a default value, such as 300 seconds.     -   [PortManager] shutdownFinalWarningDelaySeconds—How long between         the second warning and the final warning (for out-calls) when         the Call Manager is shutting down. By way of example, the value         can have a default value, such as 120 seconds.     -   [PortManager] shutdownNowDelaySeconds—How long between the final         warning (for out-calls) and forced hang-up (optionally for all         calls) when the Call Manager is shutting down. By way of         example, the value can have a default value, such as 30 seconds.     -   delayIncallAnswerAfterOutcallAnswerSeconds—How long to delay         answering the incall after the auto-transfer outcall has been         answered. This is intended to give the subscriber a chance to         answer and request a connection before the caller hears the         greeting. Optionally, this parameter is used if the         Auto-Transfer Presentation Style is Tutorial or Screening. By         way of example, the value can have a default value, such as 2         seconds.     -   [OutcallTimingCache] defaultConnectDurationMinutes—Default         duration returned if a corresponding database row is not found         (an exception is optionally also logged). By way of example, the         value can have a default value, such as 30 minutes.     -   [OutcallTimingCache] defaultWarningType—Default warning type         returned if a corresponding database row is not found (an         exception is also logged). The value optionally defaults to a         value, such as long or short.     -   [OutcallTimingCache] shortFirstWarningSeconds—Seconds, or other         time unit, of warning for first ‘short’ type warning. By way of         example, the value can have a default value, such as 120         seconds.     -   [OutcallTimingCache] shortSecondWarningSeconds—Seconds, or other         time unit, of warning for the second ‘short’ type warning. By         way of example, the value can have a default value, such as 45         seconds.     -   [OutcallTimingCache] longFirstWarningSeconds—Seconds, or other         time unit, of warning for first ‘long’ type warning. By way of         example, the value can have a default value, such as 180         seconds.     -   [OutcallTimingCache] longSecondWarningSeconds—Seconds, or other         time unit, of warning for second ‘long’ type warning. By way of         example, the value can have a default value, such as 45 seconds.     -   EnableTransferFromOutcallTui—Default value is optionally set to         true. If true, the transfer from outcall functionality is         supported.     -   MinSecondsReminingForTransferFromOutcall—The number (or greater)         of seconds, or other time unit, that needs to be available on         the connected call for the transfer from outcall to be allowed.         This prevents an outcall from being transferred if the call does         not have sufficient time to connect. By way of example, the         value can have a default value, such as 60 seconds.

Example call logging will now be described.

A CDR (call detail record) is optionally logged and stored for the incoming call and/or the auto-transferred call in association, with an identifier to associate the incoming call and the auto-transferred call. One or more of the following call details can be recorded:

-   -   An indication (such as one or more bits or alphanumeric         characters) that the call is an auto-transfer call.     -   An indication as to whether a call auto-transfer was attempted         and whether the subscriber answering the auto-transfer call         chose to take the call.     -   The auto-transfer connect duration.     -   The called number type for the auto-transfer outcall.     -   The auto-transfer connect phone number for the auto-transfer         call.     -   An indication that an auto-transfer outcall ended because the         call was transferred

With respect to connected calls, some or all of the following example information can be stored in corresponding CDR log fields

-   -   ConnectedPhoneNumber—The phone number used for an outcall for a         given call. This field is populated if an outcall was attempted         for the call, optionally even if the outcall failed.     -   ConnectDurationSeconds—The connect duration, such as the number         of seconds that the call was connected. This could be zero if         the call outcall failed, or if the call was screened but not         connected.

Example call processing system TUI (Incall) and auto-transfer processes and states from the caller's perspective will now be described with reference to FIG. 22. The caller places a call which is received at the call processing system at state 2202. At state 2204, the caller hears the ringing tone during a ringing state.

At state 2206, a determination is made as to whether auto-transfer outcall is be placed. For example, while in the ringing state, an auto-transfer outcall is placed if the appropriate conditions are met, optionally including one or more of:

-   -   The Call Manager AutoTransferEnabled configuration parameter is         set to true.     -   The subscriber is online and AutoTransferEnabledOnline is set to         true or the subscriber is offline and both         AutoTransferEnabledOffline and OfflineAnsweringEnabled are set         to true.     -   AutoTransferCallerIdRequired is set to false for the called         party/subscriber, or the caller ID for the given call is         available and not private, or AutoTransferUseMrtCallerId is set         to true.     -   AutoTransferPhoneNumber for the called party/subscriber contains         a valid phone number.     -   Either the Call Registry is not configured or there are no         outcalls in progress to the selected auto-transfer phone number.

In this example, the process stays in the ringing state until the outcall has been answered or until the ringing has been played for a predetermined amount of time (such as the time specified by the AutoTransferOutcallRingTimerSeconds parameter) or rings. If the auto-transfer outcall fails because the outcall destination is busy, the process proceeds to exit state 2208, and the caller optionally will still hear a full ring count.

At state 2210, a greeting message can be played to the calling party by the call processing system, and at state 2212 the call processing system can begin recording a message from the caller, which can then be streamed to the auto-transfer destination once the outcall process to the destination terminal is completed. At state 2214, the called party can cause the greeting and/or message recording states to be interrupted or bypassed by accepting the call as described below with respect to FIG. 23.

Example call processing system TUI (Outcall) and auto-transfer processes and states from the called party's perspective will now be described with reference to FIG. 23. At state 2302, a call is placed by a caller to the called party. The called party can be a subscriber to the call processing system services. At state 2304, a determination is made as to whether the call can be directly connected to the called party, without screening, which causes the call to ring through to the called party's phone/terminal as with a regular phone call. For example, a determination can be made as to whether the auto-transfer presentation style parameter AutoTransferPresentationStyle is set to auto connect for the called party.

If the called party has instructed that the call be directly connected to the called party, then the process proceeds to the connected state at state 2314. If the called party presses the appropriate phone key, such as the “2” key in this example, during the connected state, the call enters the handle transfer state at state 2316, wherein an attempt is made to transfer the call to a destination telephone terminal associated with the key press. If the transfer is successful, the process is done and returns to the connected state at state 2314. If the transfer is not successful, the process proceeds to the transfer failed state at state 2318, and a transfer failed message is played by the call processing system to the called party. The process then returns to the connected state at state 2314.

If the called party has not instructed that the call be directly connected to the called party, and/or if the called party has instructed that call screening be performed (such as by causing the AutoTransferPresentationStyle parameter to be set to Tutorial With Screening or Screening), then the process proceeds to the presenting state at state 806. In the presenting state, the called party is optionally informed that the call is an auto-transfer call and, unless instructed otherwise by the called party, the process enters the call screening state at state 2310.

In the screening state, the audio in progress in the original call, between the caller and the call processing system, is presented or played to the called party. Thus, for example, when prompts are being played to the original caller, the called party also hears the prompts, and when the call processing system records a message, the audio from the calling party is presented to the called party via the auto-transferred call.

If the called party presses the appropriate phone key, such as the “2” key in this example, during the presenting or screening states, the process enters the handle transfer state at state 2308, wherein the call is transferred to a destination telephone or other terminal associated with the key press, and the call can optionally be screened on the new destination terminal. When this state returns, the call enters the screening state at state 2310. By way of further example, optionally if the called party presses a transfer key, such as “2”, during the presenting state, the process will skip the rest of the presenting message and proceeds to the handle transfer state.

In the handle transfer state, an attempt is made to transfer the call to a destination telephone terminal associated with the key press. If the transfer is successful, the process is done and proceeds or returns to the screening state at state 2310. If the transfer is not successful, the process proceeds to the transfer failed state at state 2312, and a transfer failed message is played by the call processing system to the called party. The process then proceeds to the screening state at state 2310.

If the called party presses an appropriate phone key, such as “1” in this example, during the presenting or screening states, the process skips or stops call screening, and the process proceeds to the connected state at state 2314, where the call is processed as similarly discussed above.

The process can optionally be exited upon the occurrence of one or more events, including, by way of example, one or more of the following occurrences:

-   -   a called party phone hang up/call termination;     -   a connect request issued by a client application executing on a         computer associated with the called party;     -   a key press indicating that the caller called the wrong number;         or     -   the call was successfully transferred to the appropriate         phone/terminal and answered.

By way of further example, if the called party is online and the IAM client is executing on a computer associated with the called party, the call processing system notifies the IAM client of the call transfer and streams of the caller message to the IAM client. The called party can then elect to take the call via the IAM client, or instruct the call processing system to transfer the call to another phone/terminal.

Optionally, the prompts played during the handle transfer state are played to the called party only, and the caller is prevented from hearing the prompts. If a call transfer is already in progress, a transfer in progress prompt message is played. If a call transfer fails, the transfer is no longer considered in progress. The called party can press an appropriate key, such as the phone “2” key, to attempt the transfer again. Optionally, a call will only be transferred if there is more than a predetermined amount of time (MinSecondsReminingForTransferFromOutcall) left on a corresponding outcall timer. If there is an insufficient amount of time left, optionally the call processing system plays a “not enough time left” prompt. If the transfer is successful, and transfer successful prompt can be played.

The following example prompts are used in the Auto-Transfer TUI.

OfferTakeCall—“You have a call. Press 1 at any time to take the call.” OfferTransfer—“Press 2 to transfer the call to your other number.” CallForSpokenName—“This is a call for <spoken name>.” OtherTookCall—“We're sorry but someone else took the call. Goodbye.” CallerHangup—“Thank you for using CallWave. Goodbye.” EarlyCallerHangup—“We're sorry but the caller hung up. Goodbye.” FirstWarning—“You have <T1> seconds left.” SecondWarning—“You have <T2> seconds left.” Timeout—“I'm sorry but your time is up. Goodbye.” Help—“To take the call, press ONE. To disable future calls, press STAR.” NotEnoughTimeForTransfer—“Not enough time left”

Transferring—“Transferring”

TransferinProgress—“A transfer is already in progress”

For the FirstWarning and SecondWarning prompts, in this example, the ConnectDuration value determines the <T1> and <T2> values and the total allowed length of the call.

When the outcall is placed, the number provided in the outcall ANI or caller ID field is selected based on the setting of certain configuration parameter. If a first Caller ID configuration parameter is set, a number stored in the first Caller ID configuration parameter is provided as the Caller ID number. If a second Caller ID configuration parameter is set the subscriber's CVL number is used as the Caller ID number. If neither the first or second Caller ID configuration parameter are set, optionally the call processing system uses the caller's phone number as the Caller ID of the outcall. In addition, optionally a number associated with the call manager system can be included in an NPA field, and at least a part of the selected portion of the caller phone number in an NXX-YYYY field.

In situations wherein a message recording is interrupted, optionally notifications or prompts can be added to the recorded message that provides a notification or explanation for the interruption. For example, if a caller has begun recording a message and the recording is interrupted when the subscriber connects to the caller, a short explanatory prompt will be appended to the interrupted to message file, such as “Recording interrupted by call transfer.” This notification can prevent the subscriber mistakenly believing that the message was interrupted as a result of a call processing system failure.

If a user party's JAM client is online when the call processing system receives a call for the user during a call, optionally the client indicates (via a ringing tone and/or other audible notification, and/or via a text and/or other visual notification), and/or that an auto-transfer is being attempted while in the active call state. In addition, the JAM client can display a log that indicates which transferred calls were connected and how long the calls were connected. Optionally, the subscriber can initiate a manual connect request before the call processing system's Call Manager has answered the call.

Optionally, once an auto-transfer process is in progress, an JAM client “take the call” button or menu selection, that permits the user/subscriber to take the call on the JAM client terminal and/or other redirect the call, is disabled and/or not displayed. If a recording was made by the call processing system, the recording can be transferred to the JAM client terminal for later playback by the user/subscriber, and a call list can be displayed providing information regarding the auto-transferred call, including information regarding the duration of the recorded message.

Optionally, if the user/subscriber of the JAM activates the “take the call button” before the call is auto-transferred, the automatic transfer is cancelled.

The following table shows an example JAM Client call log display as a result of different call outcomes for a transferred, or attempt transferred call, although other log entry displays and information can be used as well.

Case Call Outcome IAM Call Log Entry Display 1 Not connected, <if available, Caller ID and/or Caller Name> no message No message <date> <time> left 2 Not connected, <if available, Caller ID and/or Caller Name> message left <message duration> <date> <time> 3 Connected, <if available, Caller ID and/or Caller Name> message left <message duration> <date> <time> 4 Connected, <if available, Caller ID and/or Caller Name> no message Forwarded <date> <time>, <connected phone left number and/or associated identifier> <connected call duration>

In another example process, a user can conFIG.their phone or line (e.g., a mobile cell phone) so that incoming calls are forwarded to another destination. Thus calls dialed directly to the phone number associated with the phone (or that otherwise is directed to the user's phone) can be automatically forwarded, forwarded after a predetermined number of rings, and/or forwarded in response to a user action, such as a key press (e.g., a do not disturb key, ignore call key, or other key) to a predetermined destination. The user can specify (e.g., via an account manager, and IVR, or otherwise) that calls are to be forwarded to the call processing system, such as to a virtual telephone line or a number (a phone number assigned by the call processing system to the user) or a pilot hunt group. A pilot hunt group is a group of numbers associated with a pilot number. The pilot number can also be a member of the hunt group. A hunt group enables an incoming call to be directed to an idle telephone station in a preprogrammed group when the called station is busy. In an example embodiment, when the pilot number is dialed, a “hunt” process is performed to find a vacant line (e.g., non-busy). By way of further example, calls not answered can be configured to forward to a predetermined location, such as the next line in a hunt group or to another predetermined line.

As similarly discussed above, the user may have specified that calls received by the call processing system are to be connected to a specified destination, with screening. For example, the specified destination can be the user's mobile phone. Thus, if a call is directed to the user's cell phone, the user can instruct that the call be forwarded to the call processing system, which will then connect the caller back to the user's mobile phone, with screening. Then, as similarly discussed above, the user can accept the call, further transfer the call to a second target phone or line with or without screening and with or without supervision, or have the call processing system record a message from the caller, which can be later retrieved via a computer or phone as similarly discussed above.

Thus, optionally, a user is provided with call screening via the user's cell phone, even when calls are initially dialed to the phone number associated with the cell phone.

Optionally, depending on the user's phone and/or mobile phone service provider, the user can assign different ring tones and/or ring tone volume to different received calls. For example, the phone can compare a phone number associated with an incoming call (e.g., wherein the phone number is received with the call signaling information) with numbers stored in the phone's contact database. If a match is found, and a specific ring tone is assigned to the number stored in the contact database, the phone can provide the specified ring tone.

Thus, for example, the user can assign a unique or selected tone to calls received from the call processing system to thereby identify when calls are being received from the call processing system, or from a specified caller. Optionally, the call processing number can provide a first number in the caller ID signaling field for calls without screening, and provide a second number in the caller ID signaling field for calls with screening. The user can associate a different ring tone for each number. Thus, the user can tell when a call in screening mode is being received.

Thus, in an illustrative example, a call can be received directly (without the call processing system involvement) on a called party mobile cell phone. The subscriber can press an “ignore” call key. The call is then forwarded to the call processing system which answers the calling party call (e.g., after a predetermined number of rings, such as 1, 2, 3, 4, 5 or 6 rings), provides a greeting, and asks the calling party to leave a message. The call processing system substantially immediately places an outbound call to the called party mobile phone, with screening, wherein the called party can hear the calling party and the calling party does not hear the called party. The mobile phone can display caller identification information (such as a name or phone number) associated with the call processing system and/or the calling party. The identification information can specifically indicate that the call is in screening mode. For example, a specific caller ID phone number can be used for calls in screening mode. The called party can press a “take call” key to accept the call, or press an “ignore” key to refuse the call. The call processing system optionally provides verbal or displayed prompts as to what key the called party is to press to accept or refuse a call.

Thus, as described above, embodiments of the present invention provide flexible, user definable call screening processes that can advantageously optionally be used even when the user is online. Further embodiments advantageously enable the user to define to which telecommunication terminals the screened call is to be broadcast to and under what conditions. Further, certain embodiments allow calls received at a call manager system to be transferred to a first called party communication terminal, and then to one or more other terminals.

Optionally, calls can be processed, dropped, re-originated, forwarded, and/or bridged so as to improve the call quality, reduce call costs, and/or for other reasons. For example, in one embodiment, a caller places a call via a calling terminal (such as terminal 1102 illustrated in FIG. 16) to a called party, who may be a subscriber of services offered by the call processing system 1124, as described above. The call may have been forwarded to the call processing system, or the call may have been placed by the caller to a virtual telephone line or a number associated with the called party, wherein when a call is placed to that number, the call is optionally connected at least initially to the call processing system and then optionally connected to the called party. For example, the call processing system can place an outcall to a telephone terminal associated with the called party, such as terminal 1112 illustrated in FIG. 16, and then bridge the inbound call from the caller and the outbound call to the called party, as similarly described above.

Because the call processing system is involved in receiving the inbound call from the caller and placing the outbound call to the called party, the call processing system optionally can continuously monitor the call (including voice, data, and/or signaling information) for instructions from the called party and/or the caller as described herein. For example, the call processing can monitor and detect key presses, voice commands, and the like provided by a caller and/or a called party.

The call may have been placed by the caller from a wireless phone or other phone terminal or line that has poor quality. For example, the call may suffer from echoes, static, voice delays, dropouts, and/or the like. If the called party and/or caller determine that the caller's connection is of poor quality, then either party can provide a command, via a key press or a voice command, or otherwise, instructing the call processing system that is monitoring the call to re-originate a new call to the caller or to the called party. For example, the call processing system can originate a call to the caller (with or without supervision, as described above), and bridge the call to the caller and the original (or a new) outbound call to the called party. The original inbound call from the caller can be dropped before or after the new outbound call is answered by the caller as appropriate or desired.

For example, optionally, the new call can be directed back to the caller's cell phone, which may be desirable if the caller's connection had dropped; or the call can be directed to the caller's wireline home phone number, work phone number, or number or communication device specified by the called party or the caller. Advantageously, the caller and called party can then continue their conversation with a small or negligible interruption and a higher quality connection. Furthermore, the call processing system may be able to determine through network signaling how the calling party's line was disconnected. For example, a VoIP trunk call could “fail” due to excessive packet loss, corruption, or delay, without an associated signaling channel message indicating that the call was cleanly or purposefully disconnected by the caller. This would indicate that the call disconnect was unintentional. If the call processing system determines or infers that the call disconnect was unintentional and/or if the called party is still connected to the call processing system, the system can prompt (via a voice or text prompt) the called party as to whether a callback should occur. If the called party responds affirmatively, the call processing system can perform the callback.

By way of further example, the called party (who may be a service subscriber of the call processing system 1124) receives a call from a caller via the call processing system. For example, as similarly described above, the call may have been placed by the caller to a virtual telephone line or a number associated with the called party, and thereby received by the call processing system. The telephone number may also be a phone number ported by way of Local Number Portability to the call processing system 1124. By way of further example, the call may have been placed to a conventional phone number associated with the called party, and then forwarded to the call processing system. The call from the caller may have been a local, Inter-state, Intra-state, inter-LATA, or intra-LATA toll call, such as where the caller is charged a per time unit fee or the like. The called party may want to save the caller the expense of the call, such as if a child, girlfriend, or boyfriend is calling from out-of-state.

Thus, either party can enter a key press, provide a voice command, or otherwise instruct the call processing system that is monitoring the call to re-originate a new call to the caller and/or to the called party via a specified phone number or communication device. For example, the call processing system can originate a new call to the caller, and bridge the call to the caller and the original or a new outbound call to the called party. The new call back to the caller can be to the number the caller called from, the caller's home phone number, the caller's work phone number, the caller's mobile cell phone, the caller's IP phone, or other number or communication terminal specified by the called party. In response to the entered command, the call processing system originates a new call to the specified recipient (supervised or unsupervised) and bridges the call to the caller and the outbound call to the called party.

A variety of processes can be used to specify or select the recipient phone or communication terminal to which the re-originated call is to be placed to. For example, one or more of the following processes can be used:

-   -   the called party enters or selects the caller phone number,         communication terminal, or IP address via key presses, voice         commands, or the like;     -   the caller can be voice or text prompted by the call processing         system to enter or select the caller phone number, communication         terminal identifier, or IP address via key presses, voice         commands, or the like. For example, a call participant, such as         the called party can be prompted “please enter the phone number         to which the call is to be re-originated with,” and the user can         dial the desired number. By way of further, example, the prompt         can be a voice prompts that states “press the 1 button to have         the call re-originated to the caller's home phone number, the 2         button to have the call re-originated to the caller's work         number, the 3 button to have the call re-originated to the         caller's mobile number, the 4 button to have the call         re-originated to 555-555-5555,” and so on. The prompts can         optionally be provided (and the called party response received)         during the original inbound call from the caller, during an         outbound call from the call processing system to the caller,         and/or via a client application, such as the IAM application         discussed above, executing on a computer terminal or the like         associated with the caller; and/or     -   the caller phone number, communication terminal identifier, or         IP address can be pre-specified by the caller and/or the called         party, stored in a database or other data store hosted by the         call processing system and/or a caller or called party client         system, and then automatically retrieved by the call processing         system in response to a caller and/or a called party         instruction.

The subscriber's transfer to phone number, communication terminal identifier, or IP address can be dynamically determined based on the location of the subscriber's mobile phone. The association between a subscriber locations and a list of phone numbers, communication terminals, or IP addresses is pre-specified by the caller and/or called party, stored in a database or other data store hosted by the call processing system and/or a caller or called party client system, and then automatically retrieved by the call processing system.

By way of illustration, in the following example, the caller provides the phone number to which the new call is to be re-originated to. In response to an instruction, such as a DTMF key press, (for example, a “4” key or other key press), by the called party and/or the caller, the call processing system prompts (via a voice or text prompt) the calling party to enter the phone number the caller would like the new call originated to. Alternatively, in response to a called party DTMF command, the system can just generate a tone and the called party can ask the caller to enter the call back number. Optionally, this can be configured by a subscriber through a member zone or account set-up, or it automatically happens after a specified number of uses (with a voice prompt playing after a specified timeout and no phone number has been entered). After the prompt, the caller speaks, dials, or otherwise enters or selects the phone number or communication device to be called. The number entered or selected by the caller is used by the call processing system to originate the new call, which then can be bridged with the outcall to the called party as described above. The entered number is optionally stored in call processing system memory and associated with the original calling number. Optionally, subsequent calls originated from the same original calling number would not require that the previously entered number be reentered by a call participant in order to re-originate a call to that number. Instead, the called party/subscriber can press “4”, or other designated key, and the call processing system will originate a new call to the previously entered number stored in the call processing system memory.

By way of further illustration, in the following example, the called party provides the phone number to which the new call is to be re-originated to. In response to an instruction, such as a DTMF key press, (for example, a “4” key or other key press), by the called party the call processing system prompts (via a voice or text prompt) the called party to enter or select the number the called party would like the new call originated to. Optionally, the return voice path to the caller is muted so that the caller does hear the prompt. Further, where the prompt is a voice prompt, the voice prompt is optionally mixed, and played at a lower volume than the caller's voice volume, so that the called party does not miss the conversation from the caller while the prompt is being played. After the prompt, the called party could dial, speak, or select the number to be called. The number entered or selected by the called party is used to originate the new call to the caller, which can be bridged with the outcall to the called party. The entered number is optionally stored in call processing system memory and associated with the original calling number. Optionally, subsequent calls originated from the same original calling number would not require that the previously entered number be reentered for call re-originating. Instead, the calling party (subscriber) can press “4”, or other designated key, and the call processing system will originate a new call to the previously entered number stored in the call processing system memory.

By way of still further illustration, in the following example, the phone number to which the new call is to be re-originated to is retrieved from an electronic contact database (sometimes referred to as an address book) or other data store. For example, a called party or subscriber may have provisioned a client-based or server-based address book or other contact data store that has a defined association between a potential calling party, which may also be a subscriber, and the potential calling party mobile cell number, home number, VoIP number, work number, and/or other numbers. If a call is received from one of these numbers, the called party can optionally provide an instruction, such as by pressing the “4” key or by providing an appropriate voice instruction, and the call processing system will substantially immediately re-originate back the call to a specified default number from the contact database, and/or be prompt the called party to choose between one or more of the contact database numbers.

For example, if a caller calls from a cell phone and the called party's address book contains a single association, then pressing “4” will cause the call processing system to immediately (or after a confirmation prompt and called party prompt responses) place an outbound call to the number in the address book, and to then bridge this new call with the outcall to the called party. If there are multiple entries, the called party can be asked via voice and/or text prompts to choose from the multiple entries. Callbacks can be used to auto-populate a subscriber's address book.

By way of yet further example, the call re-origination process can include a client application executing on a user's computer. The subscriber or other user may be near a computer terminal, such as a personal computer or networked television, which is running a client application monitoring the call based on information transmitted to the client from the call processing system. The information can include the caller phone number and/or name, the called party phone number to which the call was placed, the current duration of the call, and so on. The client application can be, by way of example, the Client application 1116 illustrated in FIG. 16 and discussed above, used to supervise and monitor a call.

For example, a called party may have seen the caller ID/Caller Name or other identifier presented via the client application at the beginning of the call and the called party may have optionally screened the call from their personal computer, networked television, or other computer system. The called party may have taken the call on the called party's mobile cell phone or optionally directed the inbound call to a conveniently available landline phone. Once the called party takes the call, an option is presented on the called party's personal computer that allows the user to re-originate a call back to the caller as similarly described above. The phone number can be selected from an optional pull down list presented via the client application, the called party's contact database, a number available in a call log presented by the client application, or otherwise selected. Note that a called party can call a caller back before even answering the call.

By way of still further illustration, in the following example, the phone number to which the new call is to be re-originated to can be selected from an address book stored or available on a called party's wireless phone. The called party can receive a call on the called party's wireless phone, and send a data message to the call processing system containing the phone number (using instant messaging, SMS messaging, email, and so on) to the call processing system. The call processing system then originates a call to the number provided by the called party, and bridges the new call in to the outbound call from the call processing system to the called party.

The above examples illustrate how a calling or called party can have a call re-originated and how a secondary number can be associated with the called party's calling number. In addition, these “personal” associations can optionally be exported to all or one or more subsets of subscribers or users of the call processing system services. By way of example, if a caller calls a subscriber who instructs the call processing system to re-originate a call to a number entered by the called party, the entered call back number (also referred to as a re-origination number) can be stored in a call processing system database or other data store and made available globally to all or one or more subsets of subscribers or users of the call processing system services. The next time the calling party calls a user or subscriber of the call processing service, the called party may not have to enter the callback or re-origination number, as the number is already available in the call processing system. For example, the call processing system can play a prompt to the called party instructing the called party to press a certain key or provide a voice command to re-originate the call to the already stored number.

By way of illustration, the prompt can instruct: “press the 1 button to have the call re-originated to the caller's home phone number, the 2 button to have the call re-originated to the caller's work number, the 3 button to have the call re-originated to the caller's mobile number, the 4 button to have the call re-originated to 555-555-5555,” and so on.

In addition, the call processing system provides the ability to re-originate caller and/or subscriber calls to a multiplicity of phone numbers. The multiple calls can be placed in parallel, in sequence, or use a combination of parallel and serial calling. For example, a subscriber may have configured their service to first ring their office number. Upon detecting that this first callback was not immediately answered (for example, after waiting for a predetermined delay like 6-10 seconds, or after a predetermined number of rings, such as 2 or 4 rings), additional calls can be simultaneously or substantially simultaneously placed to the subscriber's home phone number, cell phone number, and/or other phone numbers specified by the subscriber and/or selected by the system. The three (or more) calls will continue to ring until one of the calls is answered, at which time the remaining calls are abandoned by the call processing system. Optionally, instead, the calls can be configured to ring for up to a predetermined number of ring cycles or up to a fixed time, and the answered calls can then be conferenced together.

The list of multiple calling locations and associated sequencing instructions can be explicitly specified by the subscriber, automatically set by the call processing system by inferring user preferences based on past call treatment, by a combination of these methods, or using still other methods.

Other call handling processes can be used to handle unanswered re-originated calls as well. For example, if a re-originated call is not answered, the call processing system can optionally: call the intended recipient back on the original calling or called party phone number, hold the original recipient call active or on hold until the re-originated call is answered and then automatically disconnect this original call, and hold the original recipient call active or on hold until the re-originated call is answered and then conference bridge or otherwise connect the multiple calls together.

By way of further example, the subscriber can provide the phone number to which the new call is to be re-originated to. The subscriber configures or registers phone numbers with the call processing system via a web interface, a telephone user interface, a paper form, or otherwise. The phone numbers entered are optionally stored in call processing system memory and associated with the subscriber's account. In addition, “location data” can be further associated with phone numbers entered by the subscriber. This “location data” can be used to simplify the call transfer process for the subscriber. The location data can be associated with phone numbers by, for example, the subscriber calling the call processing system from a mobile phone with location capabilities and dialing through an IVR (Interactive Voice Response) system to select one of the pre-configured phone numbers to the call processing system with LBS (Location Based Services) capabilities. For example, LBS can be used to determine the geographical position of a cell phone or other terminal in a mobile network based on their cell identifier (ID). This information can then be translated into latitude and longitude information. In addition, triangulation of the mobile phone, performed using two or more cell towers, Assisted GPS, TDOA (time difference of arrival), EOTD (Enhanced Observed Time Difference), AFLT (Advanced Forward Link Trilateration), and/or other locator technologies, can be used to further refine the estimate of the cell phone location.

In addition or instead, the location data can be associated with phone numbers by the user selecting a pre-configured phone number from a list of numbers and then transmitting the selection over a data network to the call processing system (e.g., from a data application running on a mobile phone or by a user sitting at home on a broadband connection connected to a computer or other terminal, with their mobile phone nearby). The location of the pre-configured phone numbers is then known to the system. This enables the call processing system to (1) ease the interaction with the subscriber since the system would not have to prompt the subscriber as to which phone number calls should be re-originated to, (2) automatically call an alternative phone number when a user is near a particular location (3) automatically call an alternative number based on a condition such as, by way of example, a preconfigured schedule or if a subscriber's phone number is turned off, out-of-range, busy, or a ring-no-answer condition occurs (in the latter cases the call processing system could optionally re-originate calls to the last registered location).

Once a calling party's call has been transferred or re-originated, the caller or the called party can optionally transfer the call back to the original calling device or number at any time by pressing an appropriate key, such as the “4” key, providing an appropriate voice command, or otherwise.

As discussed above, the call processing system can process VoIP calls. One potential drawback to VoIP calls is that packets can be dropped or lost, or packet arrival can be delayed, which can have an adverse impact on the voice quality of the call. Optionally, the call processing system can continuously or periodically monitor a VoIP call, keep track of the number of lost packets within a predetermined time period, and/or keep track of packet latencies. If the number of lost packets within the period of time meets or exceeds a first specified threshold, or if the packet latency meets or exceeds a latency threshold stored in, and retrieved from, computer readable memory, the system optionally interrupts the call and prompts the caller to determine if the caller wants to transfer the caller inbound call from the caller and/or the outbound call to the called party to a circuit switched call or other call medium. If the called party responds affirmatively (via a key press, voice command, text command, or otherwise), the call processing system originates a new call using the specified method and/or network to one or both call participants and bridges the calls. This reconfigured call may optionally cause the caller and/or the called party the subscriber additional expense.

Further, an option to re-originate one or both calls on a circuit switched network can be offered as a user selected option, which can be triggered, for example, if the user dials the “5” key or other appropriate key.

Optionally, during a call between a caller and a called party, such as during the calls described above, the caller and/or called party can instruct the call processing system to conference-in a third party. This conferencing process can be performed using one or more of the methods described above and the call processing system can bridge and mix the three or more calls together. By way of example and not limitation: the called party or caller can enter or select the third party number via key presses, voice commands, or the like; the called party or caller can be voice or text prompted by the call processing system to enter or select the third party number; the third party number can be pre-specified by the caller and/or the called party, stored in a database or other data store hosted by the call processing system and/or a caller or called party client system, and then automatically retrieved by the call processing system in response to a caller and/or a called party instruction; or using other of the above described processes.

The call conferencing process can be invoked by way of example by the caller and/or called party dialing the “6” key or other selected key or voice command. One or more parties can optionally be integrated or conferenced into the call by repeated entries of the “6” or other appropriate key by a call participant, and then the selection and/or entry of other parties' phone numbers as similarly described above.

If a third party is unavailable, such as, for example if their phone line is busy, then the call processing system can optionally camp-on the line and add the third party when their line is freed up.

Further, embodiments can be used in conjunction with call waiting. As previously discussed, a caller can place a call via a calling terminal to a called party. The call may have been forwarded to the call processing system, or the call may have been placed by the caller to a virtual telephone line or a number associated with the called party, wherein when a call is placed to that number, the call is optionally connected to the call processing system. For example, the call processing system can place an outcall to a telephone terminal associated with the called party, and then bridge the inbound call from the caller and the outbound call to the called party. As previously described, the call processing system can constantly or periodically monitor calls being processed by the call processing system. If a new call comes in for a called party while the called party is already busy speaking to another caller on a call being processed by the call processing system, a call waiting message, tone or other prompt can be invoked. The new incoming call can optionally be screened by the called party while the called party is still listening to the original caller. The voice channel of the new call voice channel is mixed, but optionally at a lower volume, with the current call. The subscriber can then provide a command, such as by pressing the “7” or other appropriate key, to switch between calls, or the call can provide another command, such as by pressing the “8” or other appropriate key, to join the two calls to the called party together in a conference call.

Optionally, because the call processing system can continuously monitor the call, if the call processing system detects the inbound call has terminated before the outbound call to the called party has terminated, the call processing system can prompt the called party for auto-callback instructions. For example, the call processing system can offer to automatically reconnect to the called party in response to a confirming key press or voice command.

In another embodiment, a called party can instruct the call processing system to record a call while the call is in progress. As similarly discussed above, the call processing system can constantly or periodically monitor a call being processed by the call processing system. For example, during a call, the caller or called party can optionally press a “9” key or other designated key, and in response, the call processing system will record the call, including the voice communication between the caller and the called party. Once the call is completed, the recording can be sent to the subscriber (caller and/or called party) as a voice attachment to an email message; into a client application, such as client application 1116, executing on their computer system, such as personal computer or networked television; and/or optionally, the recorded call can be sent to a message store and the caller and/or called party, if so authorized, can call the call processing system to retrieve the recording as a voice message.

Optionally, the call processing system may only respond to commands (such as those relating to initiating a call re-origination, call conferencing, call recording, and so on) from a subscriber or other authorized person participating in the call. For example, the call processing system may determine if a caller is a subscriber by reading the Caller ID signaling information associated with the caller's call, and determining if the Caller ID information matches or corresponds to a phone number a subscriber stored in a database, such as the IAM database subsystem 1136 illustrated in FIG. 16. The call processing system can determine that the called party is a subscriber using a variety of techniques. If the caller's call was placed to a virtual number assigned to a subscriber, then the call processing system assumes that the call was intended for the subscriber. If the call was forwarded as a result of, for example, a call forwarding on busy, a call forwarding on ring-no-answer, or call-forward-all calls condition, then the number from which the call was forwarded can be used as a search key or index into the database to determine if number matches a subscriber's number, and that the call was forwarded from a subscriber line and is intended for the subscriber.

Other optional techniques for determining if a call participant is a subscriber include accessing a cookie or cookie-type file stored on a call participant smart phone or other communication terminal, and based on the information in the cookie or file, determining if the call participant is a subscriber. By way of further example, call participants can optionally be requested to enter a user identifier and/or password to authenticate the participant as a subscriber.

FIG. 9 illustrates an example call process. Not all states need to be reached, and the states do not necessarily need to be performed in the same order as that illustrated. In addition, certain state processes do not need to be performed serially, and two or more states processes can be performed in parallel. The call process can include additional states as well. With reference to FIG. 24, at state 2402, the call processing system receives an inbound call from a caller intended for a called party. At state 2404, an outbound call is placed by the call processing system to a communications terminal or line associated with the called party. At state 2406, the inbound and outbound calls are bridged or otherwise connected. At state 2408, the call processing system monitors the bridged call and detects when the called party or caller (as authorized) provides a re-originating instruction.

At state 2410, an outbound call is placed to the number associated with the re-origination instruction. By way of example and not limitation, the called party or caller can enter or select the number via key presses, voice commands, or the like; the called party or caller can be voice or text prompted by the call processing system to enter or select the number; the number can be pre-specified by the caller and/or the called party, stored in a database or other data store, and then automatically retrieved by the call processing system in response to a caller and/or a called party instruction; and so on. At state 2412, the outbound call to the new caller number is bridged with the existing (or a new) outbound call to the called party.

Optionally, at state 2414, the caller or called party provide an instruction to conference in one or more third parties via a key press, voice instruction, or otherwise. At state 2416, the call processing system places an outbound call to a number associated with the third party. By way of example, the called party or caller can enter or select the third party number via key presses, voice commands, or the like; the called party or caller can be voice or text prompted by the call processing system to enter or select the third party number; the third party number can be pre-specified by the caller and/or the called party, stored in a database, and then automatically retrieved by the call processing system in response to a caller and/or a called party instruction; or otherwise. At state 2418, the outbound call to the third party is bridged to the call between the caller and the called party. At state 2420, a call record command from one or more of the call participants (as authorized) is detected and received by the call processing system. At state 2422, the call processing system records the call between the caller, the called party, and/or the third party. Once the call is completed, the recording can be sent to one or more of the call participants as a voice attachment to an email message; via a client application executing on a call participant computer system; and/or sent to a message store for later retrieval. Further, the processes illustrated in FIGS. 22 and 23 can be performed in conjunction with the process illustrated in FIG. 24. For example, the called party can transfer the inbound call to another phone associated with the called party.

An example call transfer process will be described using Location Based Services, call screening to a mobile device, and transfer to a home number. With reference to FIGS. 25A-B, at state 1000, a call is received at a Call Processing System 1124 from a calling party 1102 over phone line 1134, PSTN 1104, and trunk lines 1118. The call from 1102 may have been redirected from a busy line 1114 or may have been directed to a virtual phone number assigned to the subscriber which terminates directly on the Call Processing System 1124. At state 1002A, after receiving the inbound call, the Call Processing System 1124 places an outcall using Call Manager 1108 over PSTN trunks 1118, to a mobile device 115 associated with the called party. The outgoing call to the called party's mobile device can optionally include the calling party's 1112 Caller ID, the Call Processing System's Caller ID 1124, or even the called party's personal or virtual telephone number as the Caller ID. Upon answer of the outbound call to the mobile device 115, the Call Processing System 1124 can optionally announce the call and can play a prompt to the called party instructing the caller with on how to take the call, transfer the call, conference the call and then bridges the inbound call with the outbound call at state 1004A. The talk path to the called party is muted to allow the called party to screen the call without the caller's knowledge of the screening process.

At state 1006A, if the called party is online, the Call Processing System sends a call notification including but not limited to one or more of the Caller's phone number, name, city, state, or calling device (e.g., cell phone). At state 1008A, the Call Processing System 1124 determines called party's location using Mobile Location Based Services 150 and then matches the location with a phone number from a preconfigured subscriber list stored in the Call Processing System's data base or file store 1136 or Client storage Personal Computer 1110. At state 1010A, the subscriber decides to transfer the call to a phone number 1112 to save costs and/or improve the quality of the call, by way of example. Because the system utilizes LBS to determine where to direct the call, the subscriber did not have to choose from a list where to direct the call or enter a destination phone number. At state 1012A, the Call Processing System 1124 makes a new outbound call from Call Manager 1108 using voice trunks 1118 to phone 1112. At state 1014A, upon answer of phone 112, Call Processing System 1124 conferences inbound call over line 1134 with outbound call to mobile device 115 with outbound call over 1114 to phone 1112. At State 1016A, the outbound call to mobile device 115 is terminated when called party 115 hangs-up or otherwise ends the call.

By way of further illustration, in one example embodiment the call processing system receives an inbound call from a calling party intended for a called party. The call processing system determines if a certain condition has occurred or exists. By way of example, and not limitation, the condition, can relate to the inability to connect to the called party's mobile phone device via a voice channel or to the phone general inaccessibility. By way of further illustration, the condition can be:

-   -   the mobile device being out of range;     -   the mobile device being busy;     -   the mobile device being turned off;     -   a ring-no-answer condition occurring on the mobile device;     -   a do-not-disturb condition occurring on the mobile device/line;     -   a specified/preconfigured (e.g., specified by the called party)         scheduled event occurring (e.g., time and/or day);

The call processing system then determines the called party's location via a location based service, such as described above, associated with the called party's mobile device. Based at least in part on the mobile device location, the call processing system selects a phone number stored in computer readable memory (e.g., in a database record associated with the called party). The call processing system then causes the calling party to be connected to a communication device associated with the selected phone number. For example, the call processing system can originate an outbound call to the communication device and bridge or otherwise connect the outbound call with the calling party's call.

An example call transfer process will be described using auto-callback. At state 1100A of FIG. 26, a call intended for a called party, such as a subscriber or other user, is received at a Call Processing System 1124 from a calling party station 1102 over phone line 1134, PSTN 1104, and trunk lines 1118. The call from station 1102 may have been redirected from a busy line 1114 or may have been directed to a virtual phone number assigned to the subscriber which terminates directly on the Call Processing System 1124. At state 11102A, after receiving the inbound call, the Call Processing System 1124 places an outcall using Call Manager 1108 over PSTN trunks 1118, to a mobile device 115 associated with the called party. The outgoing call to the called party's mobile device can optionally include the calling party's 1112 Caller ID, the Call Processing System's Caller ID 1124, and/or the called party's personal or virtual telephone number as the Caller ID.

At state 11104A, upon answer of the outbound call to the mobile device 115, the Call Processing System 1124 can optionally announce the call and can play a prompt to the called party instructing the caller with on how to take the call, transfer the call, and/or conference the call, and then bridges the inbound call with the outbound call. The talk path to the called party is optionally muted during this state to allow the called party to screen the call without the caller's knowledge of the screening process. At state 11108A, the subscriber selects an option to take the call. The Call Processing System 1124 opens the talk path over the connection to the mobile device 115 and the conversation between the caller and called party begins.

In this example, at state 1110A, the subscriber decides s/he would like to call the called party back (e.g., so the caller does not have to pay for the call). The subscriber asks the caller to hang-up phone station 1102 or to otherwise terminate the call, which results in the tearing down of the inbound call from the caller station 1102 over line 1134 to Call Processing System 1124. At state 1112A, the Call Processing System 1124 detects the caller call termination, such as the hang-up of station 1102, and substantially immediately prompts subscriber if s/he would like to return this call by pressing the 1 key. If the subscriber does not respond within a predetermined time period, such as 5 seconds, the process proceeds from state 1112A to state 1113A and the Call Processing System plays a “Goodbye” voice prompt and at state 1122A tears down the call to the subscriber station 115. If the subscriber presses an improper key (e.g. a key other than the 1 key), the process proceeds from state 1112A to 1114A, at which the determination is made that an improper key was pressed, a prompt is played so informing the subscriber (“Sorry, that is not a valid option”). The process returns from state 1114A to state 1112A, where the prompt regarding returning the call is replayed.

If the subscriber presses the 1 key (providing a DTMF 1) at state 1112A, indicating that the call is to be returned, the process proceeds to state 1116 and the Call Processing System plays a “connecting” voice prompt to the subscriber and transitions to State 1118A where a new outbound call from Call Manager 1108, using voice trunks 1118, to station 1102 is made.

Upon answer of the phone station 1102 at state 1120A, the Call Processing System 1124 plays a greeting voice prompt and conferences outbound call over line 1134 with outbound call to mobile device 115. When the parties finish their conversation and hang-up or otherwise provide a termination indication, calls are terminated and the process proceeds to state 1122A. (Note: if original party 1102 terminates his/her call before the subscriber, the Call Processing System 1124 will optionally again prompt the subscriber to return the call and/or call another party.)

If there is no answer at state 1118, then the process proceeds to state 1119A and the Call Processing System 1124 plays a notification, such as an “I'm Sorry, we could not reach your caller” voice prompt, and the process proceeds to state 1122A where the outbound call to the subscriber 115 is terminated.

Increasingly, people are increasingly associated with a multiplicity of communication devices, such as a work phone, a home phone connected to a switched telephone network, a phone connected to an Internet protocol network, a cellular phone, etc. Thus, it is often difficult for a caller wishing to reach a person to decide which of the many phone numbers associated with the person to call. Thus, for example, a caller may first try a work phone, and if the person is not there or does not answer, the caller may then call the person's home phone, then the person's mobile phone, etc. It would be advantageous to have a phone address, such as a single phone number, which can be used to reach a person whether the person is at work, at home, or in the car, via a mobile phone.

While certain descriptions refer to example Web page, network and telephony standards and protocols, other standards and protocols can be used as well. In addition, unless otherwise indicated, the functions described herein may be performed by executable code and instructions stored in computer readable memory and running on one or more processor-based systems. However, state machines, and/or hardwired electronic circuits can also be utilized. Further, with respect to the example processes described herein, not all the process states need to be reached, nor do the states have to be performed in the illustrated order. Further, certain process states that are illustrated as being serially performed can be performed in parallel.

Similarly, while certain examples may refer to a personal computer system, other computer or electronic systems can be used as well, such as, without limitation, an interactive television, a networked-enabled personal digital assistant (PDA), a networked game console, a networked entertainment device, and so on. While certain references are made to certain system components or services, other components and services can be used as well. Further, while certain of the following examples are discussed with respect to business users, the processes and systems described herein can similarly be used by individual, personal users. In addition, while certain user inputs are described as being provided via keypresses or by clicking on a button, optionally, user inputs can be provides using other techniques, such as by voice or otherwise. While certain phone numbers are referenced for purposes of illustration, other phone numbers or electronic addresses or locators can be used as well.

Unless otherwise specified, the term phone number refers generally to a telephonic address, such as, without limitation, a standard POTs telephone number, an E.164 phone number (ITU-T recommendation which defines the international public telecommunication numbering plan and telephone format used in the PSTN and certain data networks), or a VoIP address.

Certain embodiments provide enhanced call management services. For example, a call processing system optionally provides a mobile answering service. The example mobile answering service includes enhanced, optionally free voice mail to a user (sometimes referred to as a subscriber). The voice mail optionally provides phone access and computer access (e.g., an interactive television, a networked-enabled PDA, a networked game console, a networked entertainment device, a smart phone, etc.) to past calls and messages, while also auto-accumulating contact information. For example, the caller may dial a phone number assigned to the processing system or the caller may dial a phone number (e.g., a phone number assigned to a mobile phone device) that has calls forwarded to the call processing system, where the call is optionally answered by the call processing system.

The user may be provided with enhanced call processing services as part of the user's phone service subscription. For example, the user may be assigned a phone number (a virtual telephone number/VTN) associated with an enhanced service provider call processing system. The user may provide this call processing system phone number to others (e.g., verbally, via email, via a printed document, such as a business card, etc.). Calls placed to the call processing system phone number may be routed via the call processing system to the user mobile phone. From a caller perspective, calls to the call processing system phone number service optionally have the standard behavior associated with a mobile phone number (e.g., a call to the new number is directed to the mobile phone, unless certain conditions occur). However, because calls directed to the new number route through the call processing system, additional call processing system enabled features for inbound calls are optionally provided, such as some or all of the following services: call screening, call transfer, call conferencing, and distinctive, customizable ringback (using configurable ring back heard by callers when they call), by way of example.

In addition, the call processing system can optionally store an electronic address book and/or a call log in a subscriber account database or elsewhere. For example, a call log can include a listing of inbound and/or outbound calls (e.g., including caller/called party identifiers (e.g., caller name), caller location, phone address, time of call, length of call, etc.) and recorded messages (e.g., recorded and stored on the call processing system). The contact list can optionally be accessed via a phone client, a telecommunications client, and/or a Web site web page.

Optionally, the softswitch automatically creates a contact for a subscriber when a call is received from a phone number that does not have an associated contact list entry. The name, phone number, and/or phone number type are automatically populated in the contact if they are known (e.g., via the caller ID or other call signaling information). Optionally, when a new caller calls the user, a new contact record is automatically created and populated using signaling information (e.g., caller ID information) associated with the call.

Other services that are optionally provided to the user via the call processing system include a Follow Me Home service, which enables subscribers to automatically receive calls destined for their mobile phone on a subscriber-designated landline when their mobile phone is either turned off or out of the coverage area. The service enables subscribers to receive calls they otherwise might have missed, and enables them to save money. Subscribers can turn off their cell phone when at home or in the office and still receive their calls, saving mobile minutes in the process.

By way of further example, the call screening and call transfer services help subscribers control which calls they take and where they take incoming calls. For example, call screening enables users to listen to voice messages in real-time and, if they choose, interrupt the message to take the call. Call transfer enables subscribers to substantially instantly transfer a live cell phone call to a home phone, office phone, or another destination (e.g., by pressing an appropriate keypad key on the subscriber's mobile phone, such as the “2” key). Optionally, the user and/or system operator can configure the user's account so that a caller will be informed that a call transfer is about to take place or has taken place.

Optionally, as similarly discussed elsewhere herein, the call processing system provides voice mail service for the user's fixed work phone. For example, a user can be assigned a personal VTN (virtual telephone number). By way of illustration, when a call is placed to the VTN, the call is optionally connected to the call processing system. The call can then be connected by the call processing system to the user (e.g., by placing an outcall to a terminal associated with the user and bridging the incoming call and the out call), to a mailbox or other service or platform associated with the user. Optionally, calls placed to the VTN can be screened by the caller. Optionally, calls placed to the VTN, and forwarded to a user terminal, can be further transferred in response to a user instruction to another destination. Optionally, calls placed to the VTN can be expanded into a conference call in response to a user instruction. Incoming calls placed or forwarded to the VTN are optionally automatically transferred/connected to a user's mobile phone. However, prior to the transfer, the call processing system determines if the mobile phone is unavailable (e.g., on and within range), and if not the call is automatically transferred to another destination, as configured by the user in a user profile. For example, the call can be transferred to a fixed phone (e.g., a non-cellular phone) or a VoIP phone associated with the user. By way of further example, the call can be transferred to a computer associated with the user, wherein the computer includes a telecommunications client. Optionally, the computer and client are configured to accesses servers, such as those associated with the call processing system, through a corporate firewall to enable certain call services described herein to be provided.

For example, when the user is working at a computer (e.g., a personal computer or other networked terminal, such as a smart phone), the user's contact list and call log can be used to initiate bridged outcalls using the fixed or mobile phone. This service is optionally promoted to the corporate IT department and offers self-administration of user accounts. Optionally, calls can be provided to a receiving computer or other terminal (such as a dedicated VoIP phone) using VoIP. Call conferencing may be used as well.

As similarly described herein, optionally, a single phone number (e.g., a VTN) associated with a subscriber can be used to reach communication devices (e.g., a mobile phone, a work fixed, landline phone, a home fixed, landline phone, a VoIP phone, etc.) associated with different lines and/or carriers. Optionally, the single phone number is provided in call signaling, such as in a Caller ID field, associated with a called placed from the different subscriber communication devices so that the number is automatically published to the people called (e.g., appears in a Caller ID display or other call identifier display associated with the called party). The transfer and conferencing call management functions are optionally made available by the system on inbound calls to the subscriber and on outcalls placed by the subscriber. Optionally, mobile location information is used to help make routing choices. A contact list/electronic address book can be provided via a mobile phone, a user computer (e.g., via a telecommunications client, a browser, or otherwise), or other networked display device. For example, a given contact list record can include some or all of the following data and/or additional or different data: name, phone numbers with phone number type designations (work, home, mobile, VoIP, etc.), email address, physical address, SMS/MMS address, contact title, contact employer, etc. Optionally, the VTN is integrated into the mobile network via an MVNO arrangement and support for Local Number Portability to provide the foregoing services.

FIG. 33 illustrates an example contact database user interface. In this example, the user interface is accessed via a browser from a remote computer system. The illustrated user interface includes fields for a contacts name, phone number, and email address. In addition links (Invite, Reinvite) are provided for certain contacts which, when activated cause an invitation to the corresponding contacts to be initiated, wherein the invitation describes call processing services that may be subscribed to. Optionally, the invite link is provided when the contact has not yet been sent a communication via the softswitch or other designated system to try certain services. If an invitation had previously been sent, a Reinvite link is optionally provided, which, when activated, causes a follow-up invitation to be issued to the contact. Optionally, subscribers who click on or otherwise activate the Invite link for contact that does not have an email address entry are asked to enter an email address first. Tabs are provided (e.g., rewards center, call log, phone book, settings, account info, and/or help tabs) which when selected cause corresponding user interfaces to be presented.

Certain optional embodiments promote services disclosed herein to potential users, such as individual business employees. Optionally, certain services (e.g., a voice mail service, call log service that can be accessed from a computer-based terminal, a call forwarding service, a message forwarding service, etc.) disclosed herein are provided at no additional cost to a user to encourage users to try and adopt the services. Optionally, users can setup their service without support of IT (Information Technology) personnel.

As users use the service, they may disseminate advantages regarding the enhanced services within their company directly and through use of the features that promote services to others. As more employees utilize the services, the employees are likely to request or encourage the IT department to more broadly utilize the service within the company so that others can take advantage of the services and advanced features. The IT department can then contact the service provider and obtain a desired number of employee licenses for the desired services. Optionally, the IT department administers employee accounts via a web interface provided by the service provider.

As use grows and there is a desire to have the possibly reduced cost and efficiencies associated with the use of a single phone number for reaching an employee at work, home, and/or on a mobile device, the IT department may contract for still additional enhanced services.

Optionally, certain services are provided without a financial charge, but are provided with promotion features to facilitate adoption of the service and/or other services within a company. For example, certain promotion messages may be played to people calling a subscriber, or to people being called or contacted by the subscriber. For example, if a caller leaves records a message for a subscriber on a call processing, the subscriber optionally can utilize a user interface (e.g., provided by the telecommunications client) to forward the recorded message (e.g., as a file or a link to a file) to a recipient, wherein the email contains a promotional message (e.g., a text and/or multimedia message), encouraging the user to try the service. Similarly a contact (e.g., accessed via the telecommunications client) can be forwarded by the subscriber, wherein promotional information is attached to or associated with the contact file. Further, when a caller leaves a message on the call processing system, optionally a trailer prompt is played promoting one or more call processing services. The message can be played before or after the caller records the message.

The following is a glossary of abbreviations used herein:

GLOSSARY AA Automated Attendant BCM Business Call Management BS Base Station DID Direct Inward Dialing HLR Home Location Register IP Internet Protocol IT Information Technology LERG Local Exchange Routing Guide LNP Local Number Portability MA Mobile Answering

MFI Mobile/Fixed Inbound call

MFON Mobile/Fixed One-Number MMS Multimedia Messaging Service MSC Mobile Switching Center MVNO Mobile Virtual Network Operator RTP Real Time Transport Protocol SIP Session Initiation Protocol

TYF Tell Your Friend service promotion (e.g., communicated by subscribers to non-subscribers).

VLR Visitor Location Register

An overview of an example embodiment will now be described. An example call processing system (which is sometimes referred to as a softswitch) is described below which can receive and forward voice messages, enables users to screen and transfer calls and to initiate conference calls, and optionally provides BCM services. The call processing system includes an interface to the PSTN to manage inbound and outbound telephone and/or fax calls, and optionally includes an interface to the Internet to manage communications between online IP client devices and call processing system servers.

The call processing system optionally includes an online presence detection Internet Session Management subsystem, which monitors the status of subscriber data terminals to determine subscriber terminal availability for call handling services. A shared Media Storage (MS) subsystem, which persistently archives the caller's voice messages and associated signaling information (e.g., the caller's phone number, name, charge phone number, account number, or other identifier), the called party/subscriber's personal greeting(s), incoming fax communications, and information related to the foregoing, is optionally further included. The call processing system optionally includes a database (DB) subsystem in which called party/subscriber call processing system service parameters (e.g., call answering, call transfer, voice mail, call screening instructions, etc.).

One or more of the foregoing subsystems can be hosted on the same computer system (e.g., a server), or subsystems can be hosted on separate corresponding computer systems. If the foregoing subsystems are hosted on different computer, they are optionally interconnected via a wired or wireless Local Area Network (LAN) and/or via a Wide Area Network (WAN).

The call processing system service optionally works with the “Call Forward On Busy” feature of a standard or non-standard phone line to answer calls (e.g., while the subscriber is online and is using the phone line to access the Internet or is using the line to talk to another party). Thus, if the user's line is busy, the call is forwarded to the call processing system. The call processing can also process calls that are received as a result of a call forwarding on ring-no-answer condition, or a call-forward-all calls condition. The call processing system can also receive calls that are not forwarded, but are instead dialed to a phone number that is consistently answered by the call processing system and optionally associated with the subscriber. Optionally, after answering a call, the call processing system plays a greeting to the caller after which the caller can leave a voice message which is recorded by the call processing system. The recording can be streamed in substantially real-time, or emailed or downloaded over the Internet or other network to a user computer system or phone as described herein. Optionally, the subscriber can elect to interact with the caller while they are still on the line or can call them back at a later time.

The call processing system can communicate with a variety of subscriber computer terminals (e.g., a personal computer, a smart phone, the work computer illustrated below, etc.). The computer terminal can optionally be equipped with a Voice over Internet Protocol (VoIP) software module and a headset or a handset, including a microphone and speaker, allowing voice communications to be conducted over a computer network, such as the Internet. VoIP communicates information via packet switching, which opens a connection just long enough to send a small packet of data. Each packet includes a destination address informing the network where to send the packet along with the actual voice data payload. If the receiving station is also a VoIP terminal, then when the receiving terminal receives the packets, VoIP software executing on the receiving terminal reassembles the packets into the original data stream. The data stream is then converted to a voice signal. If the receiving station is a conventional telephone, then a VoIP gateway converts the packets into a voice signal that is then connected to the PSTN.

Optionally, the VoIP process is performed using the H.323 standardized protocol established by the International Telecommunications Union (ITU). Advantageously, H.323 provides specifications for real-time, interactive videoconferencing, data sharing and audio applications such as IP telephony. In addition or instead, the Session Initiation Protocol (SIP) can be used. SIP is generally more efficient than the H.323 protocol as SIP is specifically intended for IP telephony. In addition or instead, proprietary protocols, such as Skype protocol, can be used (e.g., where multi-vendor interoperability is not needed).

The subscriber computer terminal can optionally host a browser or other network resource user interface, an email application for receiving and sending emails, and an instant messaging application (e.g., IAM).

Optionally residing and executing on the computer terminal is a communications management client application. In one example, when a user or subscriber connects to the Internet using, for example, a dial-up ISP, the client application executing on the subscriber's computer terminal makes the subscriber's online presence known to the call processing system. Presence detection is optionally performed by the call processing system polling or pinging the computer terminal via the telecommunications client application, or by the telecommunications client application transmitting a “Login/I'm alive” message and subsequent periodic “keep alive” messages to the call processing system. Just prior to the normal termination of the online Internet session, the client application optionally sends a “Logout” message to the call processing system.

If, rather than using a dial-up connection, the user or subscriber is using a broadband connection, such as a DSL line or cable modem, the client application optionally becomes active when the subscriber computer is turned on or powered up and stays on until the user manually shuts down the client application, or the computer is turned off or powered down.

The subscriber can install the telecommunications client for use on more than one computer-based system (e.g., a work computer, a laptop, a home computer, a smart phone hosting an appropriate operating system, such as Windows mobile, Linux, Palm OS, or other compatible operating system). Optionally, multiple instances of the telecommunications client can be simultaneously online with the softswitch. Optionally, the online instances of the client are notified by the softswitch of an incoming call and are presented with the call. Similarly, online instances of the client are optionally synchronized by the softswitch with call or contact updates.

The telecommunications management client application is used to provide and display one or more of call and message information to the subscriber (e.g., information regarding incoming calls, call logs), contact information via a contact database/electronic address book (e.g., including some or all of the following: name, title, company, phone number(s), instant messaging address, email address, etc.), information regarding credits or bonuses earned by the subscriber (e.g., wireless phone calling minutes earned as a result of callers calling the subscriber, earned as a result of invitations from the subscriber to others to subscribe to call managing services, earned as a result of invitation acceptances, etc.), or the bonuses redeemed by the subscriber. The telecommunications management client enables a subscriber to listen to recorded messages to provide call handling instructions to the call processing system (e.g., take the call, forward the call, place a conference call, take a message, refuse the call, etc.). Thus, the telecommunications client is available to the subscriber for viewing calls and contacts (e.g., via a tabbed display). The client can, by way of example and not limitation, be hosted on a computer (e.g., a personal computer, a smart phone, an entertainment center) running Windows XP, 2000, 98/ME, or 95, Windows Mobile edition, Sun Solaris, Apple OS X, Linux, or other operating system. Some or all of the information and functions available via the telecommunications client or optionally available via Web pages hosted by the softswitch or other system and which can be accessed via a browser.

The subscriber's call log is displayed in response to a subscriber action (e.g., when a Calls tab is selected on the telecommunications client user interface). The subscriber's call lists calls that were received by the softswitch (e.g., call forwarded from the subscriber's mobile phone to the softswitch). In an example embodiment, the most recent call is listed first and any new, unreviewed calls are highlighted or otherwise identified or emphasized. Some or all of the following information is displayed for a given call: name (e.g., the name associated with the caller phone number in the subscriber's contact list, if available; the caller's name, if available from the call signaling information; otherwise “Unknown”, where “Unknown” optionally appears as a link and when clicked opens the edit contact window with some or all of the call's signaling information displayed in pre-populated fields), phone number from the CallerID signaling field (or, if the call signaling information indicates that the call is designated as private, “Private” is displayed, or if callerID information is unavailable, “Unknown is displayed), call outcome (e.g., if the caller left a message, an indication that a message was left and a message duration, if the caller was connected to the subscriber, an indication that the connection was made and the call duration, otherwise, a no message left indication is provided), and the local date/time of call (optionally including a time zone indicator).

Optionally, if a call was placed to a VTN associated with the subscriber, the call log will list both the VTN (or provide an indicator, such as an icon, that the call was placed to the VTN) and an indicator (e.g., an icon, name, and/or phone number) as to which line the subscriber took the call. For example, if a caller called the subscriber's VTN, and the subscriber took the call on the subscriber's mobile phone, the call log entry can so indicate.

Clicking on or otherwise moving a cursor to a call entry in the call log selects the call, and then applicable button controls then apply to that call. Optionally, the first time the call log is displayed in a given session, the first (most recent) call is selected by default. Optionally, when switching between call log and contacts user interfaces, the previously selected call is remembered and redisplayed when the call log is again selected.

If a message (e.g., a recorded message from a caller) is associated with the call, the message can be played by clicking on a Play button. While a call is playing, a sliding cursor shows play progress. Playing can be stopped at a desired point by clicking a stop/pause button, or a play cursor can be repositioned to restart play at another point. Optionally, call volume can be adjusted via a client application call control and/or via a separate operating system or other volume control.

A Delete control is provided, which, when activated, causes the deletion of a call log entry. An Undo control is optionally provided, which, when activated can undelete previously deleted calls (e.g., up to a certain limit, such as the last 10 deleted calls).

A Forward control is optionally provided, which, when activated causes information regarding the currently selected call to be forwarded to a designated recipient (e.g., via email, SMS, MMS, instant messaging, etc.). Activating the Forward control optionally causes a drop down list of the subscriber's contacts, or a portion thereof, to be displayed. Optionally, the subscriber contacts are listed alphabetically by name, and optionally contact entries without a name are excluded or listed after those entries with a name.

An Invite button control provided is provided (optionally, when the contact has not yet been sent an email or other electronic invitation via the softswitch to try certain services (e.g., TYF email or other electronic communication) to the given address (e.g., email address) or if the address is blank; if an invitation had previously been sent, a Reinvite control is optionally provided. Optionally, subscribers who click on or otherwise activate the Invite button control for a blank email address are asked to enter an email address first; otherwise, both Invite and Reinvite display a TYF form with this entry's email address pre-populated.

The subscriber's call log is optionally stored on the subscriber's computer and is available when the application client is offline. As similarly discussed elsewhere herein, the call log stored on the subscriber's computer is synchronized with the softswitch when the telecommunications client logs in to the softswitch, and synchronization is optionally periodically performed while online (e.g., every minute, every two minutes, or at other interval) while the client is online.

Optionally, when an incoming call is received, the telecommunications client is automatically maximized or increased in size if it is currently minimized, the information about the caller (e.g., name, phone number, and/or city/state) is displayed, and the message being left by the caller is played, unless the speaker mute control is activated, as discussed below. When the call completes, the call is optionally displayed as the first call in the call log and it is highlighted or otherwise emphasized (e.g., via a new call icon) to indicate it is a new call. Optionally, an indication is provided (e.g., via a blinking icon) that new calls have been received until the indicator is clicked on or the new calls in the call log are clicked.

If incoming calls are received by the softswitch when a telecommunications client is offline, when the telecommunications client goes online and a session is established with the softswitch, information related to those incoming calls is transmitted by the softswitch to the client. The call information to the calls is optionally displayed at the top of the call log (or at another designated position) with highlighting or other indicator that indicates the calls are new calls, and optionally, an icon is blinked or otherwise emphasized to indicate that new calls have been received.

Optionally, the telecommunications client has a user accessible control (e.g., with a speaker icon) for muting telecommunications sound signals that would otherwise be produced by the host computer speaker. When clicked on or depressed, sound from the client application to the speaker is muted, and when not depressed or when clicked on again, the sound is unmuted. Optionally, the subscriber can control the default state/position of the mute control for incoming calls (e.g., via the option setting “Enable speaker during incoming calls”). Optionally, by default the client application sound to the speaker is not muted for incoming calls. If the user clicks on a message entry in a call log to play the message (or otherwise activates a play message control), optionally the mute control automatically changes to the unmuted position/state, and again changes to its specified default position/state if an incoming call is received. The mute control can be clicked while playing a message or receiving a call to change the speaker/mute behavior.

As discussed above, Internet protocol telephony, such as VoIP (voice over Internet protocol), may use, in whole or in part, the Session Initiation Protocol (SIP) as the signaling protocol. SIP is a standardized signaling protocol which can be used for Internet conferencing, telephony, presence, events notification and instant messaging. The Session Initiation Protocol is currently an Internet Engineering Task Force (IETF) standard protocol. There may be several versions and implementations of SIP, including non-standard versions. SIP, by way of example, enables one or more of the following services to be provided, using proxy servers and end user client systems:

-   -   1. Call forwarding: call forwarding can be provided in response         to one or more of the following conditions: ring-no answer,         busy, unconditional call forwarding, address manipulations (such         as permanent numbers (e.g., 700 numbers), free phone numbers         (e.g., 800, 866 numbers), and paid information numbers (e.g.,         900 numbers)).     -   2. Call recipient and calling number identification     -   3. Personal mobility     -   4. Caller and call recipient authentication     -   5. Invitations to a multicast conference     -   6. Basic Automatic Call Distribution (ACD)

A call may optionally be routed partially over the Internet, using SIP or other protocols, and partially over a circuit-switched network, such as a PSTN (public switched telephone network). The PSTN may utilize a variety of signaling and other standards, such as the SS7 signaling protocol.

SIP is a request-response protocol. In one embodiment, SIP can be used for establishing, manipulating and tearing down user sessions, wherein several users can optionally participate in a session. A session can optionally involve multimedia elements including audio, video, instant messaging, and/or other real-time data communications. By way of further example, a session can be an Internet multimedia conference, an Internet telephone call and/or a multimedia distribution session. Optionally, session members can communicate using multicast and/or using a mesh of unicast relations.

SIP can optionally run over UDP (User Datagram Protocol), TCP, IP, ATM, X.25 and/or other protocols. In one embodiment, SIP can work in the Application layer of the Open Systems Interconnection (OSI) communications model.

In one embodiment, SIP invitations are used to create sessions. The invitation can carry session descriptions which enable participants to agree on a set of compatible media types. SIP enables user mobility by providing proxy services and redirecting requests to the user's current location. For example, users can register their current location so that calls can be directed to a telephone or other terminal corresponding to the location.

An example system that can be used to support SIP can include some or all of the following components:

1. An endpoint component, sometimes referred to as a user agent (UA), which can be a hardware and/or software device implementing or compatible with SIP, such as an Internet Protocol (IP) phone or other terminal. The endpoint components can include a client used to initiate calls and a server used to answer calls. By way of further example, a SIP Proxy, a SIP phone, a call processing system, and so on, can be SIP endpoints.

2. A SIP network server that handles signaling associated with one or more calls. By way of example, in an optional embodiment, the network server provides name resolution and user location. The SIP network server can include one or more additional servers. For example, the SIP server can include a Register server used to receive registration messages from endpoints regarding current user location. Using a mapping database, the Register server can map the SIP addresses with the physical location or locations in the domain where the endpoint is located. The SIP network server can also include a proxy system that transmits call setup and tear down information and optionally forwards SIP messages to multiple proxy servers, creating a search tree, in order for the SIP messages to reach their destination. In addition, a SIP proxy can discover endpoint characteristics of an endpoint by consulting a list of registration templates, including dynamic configuration parameters, for that endpoint. The network server can also include a SIP Redirect server that enables endpoints to locate a desired address by redirecting one or more of the endpoint to another server.

SIP addresses can be the form of uniform resource locators (URL). By way of example, SIP addresses can optionally be embedded in Web pages. In certain applications, a user can click on a SIP address embedded in a Web or other electronic document, and in response, a call can be placed from the user terminal to the SIP address, and the user can then talk to the person or system associated with the SIP address and/or send data files to the person or system associated with the SIP address.

When making a SIP call using a SIP terminal, the SIP terminal locates the appropriate server and then sends a SIP request, such as an invitation that initiates a session. The request may directly reach the intended call recipient, or the request may be redirected or may trigger a chain of new SIP requests by proxies. If a call is to be routed through a number of different proxy servers, a redirect server can be used. When a caller's user agent sends an INVITE request to the redirect server, the redirect server contacts the location server to determine the path to the called party, and then the redirect server sends that information back to the caller. The caller terminal then acknowledges receipt of the information. The caller terminal then sends a request to the device indicated in the redirection information (which could be the call recipient terminal or another server that will forward the request). Once the request reaches the call recipient terminal, the recipient terminal transmits a response and the caller acknowledges the response.

The Real Time Protocol (RTP), Real Time Control Protocol (RTCP), and/or other appropriate protocols can be used to send audio using packets over the Internet to allow the caller and call recipient to verbally communicate. By way of example, the packets can optionally be UDP packets.

Optionally, calls directed to one more selected numbers can be routed by a SIP provider to a call processing system optionally operated by a separate entity than the SIP provider. The call processing system can provide telephone services by integrating with one or more Internet Services Providers (ISP), SIP providers and/or other telephony providers.

FIG. 27 illustrates example system components and call flows used to provide certain call processing features. In this example, a caller initiates a call to the subscriber's mobile phone and the call is routed to a call processing system including a softswitch (e.g., software that performs switching on a server) associated with an enhanced call process service provider. In this example, the call is not answered using the mobile phone.

The subscriber, when registering for the MA service, changes or sets the “no answer call forwarding” of their mobile phone to forward to a pilot number (e.g., 775-665-1234 or other designated number or address) associated with softswitch, instead of the voice mail system of their wireless carrier. The pilot number can be a member of the hunt group. A hunt group enables an incoming call to be directed to an idle telephone station in a preprogrammed group when the called station is busy. In an example embodiment, when the pilot number is dialed, a “hunt” process is performed to find a vacant line (e.g., non-busy). By way of further example, calls not answered can be configured to forward to a predetermined location, such as the next line in a hunt group or to another predetermined line.

Referring to FIG. 27, an example call handling sequence in this scenario is as follows:

At state 101A, a caller dials the phone number of the subscriber's mobile phone. The number is recognized in the PSTN as associated with or owned by a corresponding wireless carrier, and so the call is routed to a Mobile Switching Center (MSC) serving that number.

At state 102A, the MSC determines that the mobile phone is accessible (e.g., the mobile phone is on and within range of a cellular tower) and not roaming, so the MSC routes the call to the mobile phone via a Base Station (BS) currently serving the mobile phone. The mobile phone is not answered in this example, and so at state 103A the MSC consults the Home Location Register (HLR) for this number and determines that calls to the number are forwarded on a “no-answer” condition to a designated pilot number (e.g., 775-665-1234 or other designated number or address) serviced by the softswitch.

At state 104A, the MSC forwards the call to the softswitch, which answers the call, determines that the call is for a subscriber, accesses the subscriber's account configuration (e.g., which includes some or all of the following: subscriber call processing, transfer, screening instructions, subscriber work and home fixed phone addresses, mobile phone address, information identifying information related to one or more telecommunications clients associated with the subscriber, etc.), plays the subscriber's personal greeting (if one exits), a spoken name greeting, or a default system greeting, and begins recording a message from the caller.

At state 105A, if the computer-based communications management client application (sometimes referred to as a PC Client) residing on the subscriber's work computer (or other designated terminal) is currently logged into/communicating with the softswitch, the call is optionally also routed to the work computer via the Internet and then passes through the corporate firewall to reach the work computer. In this example, the firewall is penetrated by virtue of the computer-based client initiated session originating from the work computer over a TCP/IP, or other appropriate connection. For example, the telecommunications client optionally automatically adjusts its interface to the softswitch as needed to penetrate a corporate firewall. For example, the client can determine certain firewall properties or conditions, and at least partly in response choose an interface, optionally, the most efficient available interface for the given firewall conditions. Optionally, the telecommunications client periodically tries to alter the interface it is using to determine if there is a more efficient interface for the current firewall conditions, and if so, uses the altered interface.

Optionally, if the telecommunications client cannot access the softswitch for a given reason, including not being able to penetrate the firewall, corresponding feedback is provided to the subscriber (e.g., an icon in the system tray is shown with a yellow X or other failure indication). If this failure condition persists beyond a certain period of time or after a certain period of retries, optionally the subscriber is instructed to contact customer care (e.g., by phone, form, email, or otherwise).

At state 106A, the subscriber can screen the call via the work computer. For example, the caller can be connected to the subscriber over a half-duplex talk path, where the subscriber can hear the caller, and the caller cannot hear the subscriber. Mute and volume controls are provided so that the user can avoid broadcasting the call to other employees. After the call is over, the softswitch and/or client application inserts an entry in the client application's call log for the new call and the associated voice message. The subscriber can provide a playback instruction (e.g., by clicking on a playback control or the log entry), and the message is played back via the client application using the host computer audio system and speakers, enabling the subscriber to review the recorded message. Messages are optionally retained in the softswitch and/or on the subscriber's work computer (or other terminal) for a predetermined amount of time (e.g., 30 days), or indefinitely

At state 107A, when the call is over (e.g., the caller or called party hang up to terminate the call), the subscriber's contact database is optionally updated to include this call. If the call is from a caller that already has an entry in the subscriber's contact database (e.g., as determined by comparing the Caller ID or other identification associated with the call to corresponding identification information in contact database records), call frequency data for an existing contact is updated to include the new call (e.g., a call frequency counter is optionally provided for a given contact that keeps track of how many calls are received from the contact as an overall total and/or a total for a specified period, such as the last twelve months). If the caller identification information does not correspond to an existing contact entry, the system optionally creates a new contact including caller name and city/state location, wherein some or all of the foregoing information is auto-populated into the contact record using call signaling information. By way of example, the contact database/list can be stored in a remote database for later access and/or on the subscriber's computer or other terminal. Optionally, if multiple copies of the subscriber's contact database are kept, the host systems can synchronize over a network and update their respective contact databases.

At state 108A, a message (e.g., a text message, such as an SMS message, MMS message, email, or other communication) is sent to the subscriber's mobile phone via an Internet-connected gateway (or otherwise) informing the subscriber that a call was missed and a message was left. The subscriber can then ask the softswitch to playback the message, forward the message, or otherwise process the message. The subscriber has the option of requesting that notifications regarding missed calls be provided via an email, which can contain a link to the message or a file containing the message, if any.

The subscriber also has the option of retrieving the message that was left via a communications client, via a phone client, via a website (e.g., using a browser), or via a Member Mobile Zone (e.g., a Web site/page that provides a subscriber with help and/or an account management user interface via which the user can perform feature configurations which are then stored in memory) which is optionally hosted on the softswitch or other server. In an example embodiment, the phone client is accessed by dialing a pilot number (such as 775-665-1234, or other designated number, address or locator).

If the access is performed from the subscriber's mobile phone or other phone having a phone address registered in the subscriber's account as belonging to or associated with the subscriber (e.g., the subscriber's home phone address, work phone address, etc.) which the subscriber has designated for account access and instant message playback without having to enter a password, the phone client optionally immediately begins message playback (e.g., receiving/reviewing messages). Optionally, if the user does not use a designated phone, but wants to retrieve the messages using another phone, the subscriber is optionally requested to enter identification information (e.g., the designated mobile phone number, user identifier and/or a password). In addition, the subscriber's personal greeting can be recorded via the phone client or computer-based client, or otherwise.

Example processing of Mobile/Fixed Inbound calls will now be discussed. FIG. 28 illustrates example system components involved in providing BCM Mobile/Fixed Inbound call functionality. VTNs are optionally used to provide expanded call routing control. Optionally, a call forwarding service is provided where calls to the subscriber's business or other fixed phone (e.g., a phone connected to a PSTN, PBX (Private Branch eXchange), or Key system) are forwarded to the softswitch. Call routing within an entity, such as a corporation or other organization, or at other locations, may be performed via Centrex, traditional PBX, IP PBX, other unconventional PBX, Key system, or otherwise.

The softswitch optionally handles corporate/organization call switching (e.g., using a PBX or other system) by routing calls through a corporate PBX and associated Auto-Attendant (AA). With reference to FIG. 28, PBX/AA generically refers to the corporate switching infrastructure, which is optionally embedded in the PSTN, (e.g., as with Centrex, which provides switching at the central office instead of at the customer's premises).

The process illustrated in FIG. 28 sequences through an example call scenario in which a caller initiates a call to the subscriber's VTN, and the softswitch substantially simultaneously routes the call to the subscriber's fixed phone and computer-based telecommunications client. In this illustrative example, the subscriber screens the call (e.g., via a half duplex talk path), takes the call (wherein a full duplex talk path is established), and then later requests the softswitch transfer the call to the subscriber's mobile phone.

At state 201, a caller dials the VTN assigned to a subscriber. At state 202, the phone address is recognized in the PSTN as owned by/associated with a VoIP Service Provider, and so routes the call to the VoIP Service Provider switch serving that phone address. At state 203, a SIP Proxy (which optionally is provided by or operated by a third party) converts the PSTN call to SIP (or other desired protocol) and transmits a message to the softswitch informing the softswitch of the call.

At state 204, the softswitch determines that the call is for a subscriber, determines the subscriber owning or associated with this VTN, accesses the subscriber's account configuration (e.g., which includes some or all of the following: subscriber call processing, transfer, screening instructions, subscriber work and home fixed phone addresses, mobile phone address, information identifying information related to one or more telecommunications clients associated with the subscriber, etc.), and dials the subscriber's fixed phone address. In this example, the fixed phone sits behind a PBX and there is no DID inbound call routing, so the softswitch performs a two-stage dialing process to get through the PBX and Auto Attendant. Other embodiments can have different configurations. For example, other embodiments can have DID inbound call routing, wherein as calls are presented to the PBX, the address that the caller dialed is also provided, so that the PBX can decide which person/extension to route the call to.

At state 205, the subscriber answers the fixed phone and screens the call (e.g., hears the message being left by the caller, wherein the path from the subscriber to the caller is muted so the caller cannot hear the subscriber). If the call had not been answered within two rings (or other designated number of rings or period of time), the softswitch would optionally have next automatically attempted to deliver the call to the subscriber's mobile phone by placing an outcall to the phone address assigned to the mobile phone.

At state 206, the softswitch routes the call to the subscriber's work computer (optionally at substantially the same time the call is being routed to the fixed phone) through a corporate firewall, so that the subscriber also has the option of screening the call via the work computer using the telecommunications client. Optionally, the softswitch instructs the client Serial Not to play a ringing sound via the computer, as the call is being presented in parallel to the subscriber's fixed phone, which is already ringing.

At state 207, the subscriber presses 1 on (or provides other designated input via) the subscriber's fixed phone to take the call. The softswitch detects the corresponding DTMF signal (or other designated input) and opens a two-way talk path between the caller and the fixed phone.

At state 208, in this example, while talking, the subscriber decides to go to a meeting at another location, and so presses 2 (or provides other designated input) to transfer the call to the mobile phone so that the subscriber can continue the conversation while walking or driving to the meeting.

At state 209, the softswitch detects the DTMF tone (or other designated input) corresponding to the subscriber instructions and dials the subscriber's mobile phone address. The call is delivered to the mobile phone via the PSTN, MSC, and BS.

At state 210, the subscriber answers the mobile phone. At this point the caller, the mobile phone, and the fixed phone are temporarily conferenced together. When the subscriber hangs up the fixed phone, the call leg to the fixed phone is dropped, and the call between the caller and mobile phone is maintained. The subscriber and caller can then converse, with the subscriber using the mobile phone.

In the foregoing example, the subscriber elected to have the call routed to a mobile phone. Optionally, other transfer destinations can be presented to the subscriber and/or specified by the subscriber. For example, optionally the subscriber can select from a number of routing choices that are based on simultaneous ring or serial ring of the available destinations (e.g., a work fixed phone, a telecommunications client, a mobile phone, and/or a VoIP phone). Optionally the subscriber can also define the call handling to be time-of-day based. For example, the subscriber can specify via a user interface (e.g., presented via the telecommunications client, a Web page or otherwise) that during certain hours and days (such as hours that correspond to the subscriber's working hours and days), calls are not be routed to the subscriber's home phone, and optionally that the routing choices should not include the subscriber's home phone. Similarly, the subscriber can specify via the user interface that during certain hours and days (such as outside of work hours), calls are not be routed to the subscriber's work phone and may be routed to the subscriber's home phone, and optionally that the routing choices should not include the subscriber's work phone.

If the subscriber chooses not to publish the subscriber's VTN (e.g., instructs that the VTN number be blocked, marked as private, or not providing in the signaling information on outgoing calls) and instead continues to have callers call either the subscriber's fixed phone or mobile phone (e.g., using the phone numbers assigned to those phones by the corresponding carriers), the example scenario below and illustrated in FIG. 29, may be more representative of how certain calls would be handled. In this example scenario, the caller calls the subscriber's fixed phone, and rather than answering the fixed phone when it rings, the subscriber lets the call be auto-forwarded (based on forwarding configuration instructions provided by the subscriber or the subscriber's agent) to the softswitch after two rings (or other designated number of rings or period of time, optionally configured by the carrier and/or the subscriber). The softswitch then presents the call to the subscriber via the telecommunications client, via which the subscriber can screen the call (e.g., by listening to a message as it is being recorded by the caller over a half duplex talk path so that the caller cannot hear the subscriber) and the subscriber can choose how the call is to be handled.

At state 301, a caller dials a phone number associated with a landline, fixed phone, and the call is routed through the PSTN to the organization's PBX. The call could instead have originated from a phone inside the organization and similarly routed through the PBX to the subscriber's fixed phone.

At state 302, the fixed phone rings, but in this example, the subscriber does not answer the fixed phone (e.g., because the subscriber prefers to deal with the call on the subscriber's computer or other terminal). The subscriber optionally has the ringer on the fixed phone set to silent or nearly silent so that the phone ring does not disturb officemates.

At state 303, the call auto-forwards after two rings (or other designated number of rings or time period) to the softswitch because the subscriber's IT department (or other person or entity) has set up this fixed phone and/or associated line to forward calls to the softswitch on a “No Answer” condition (that is, when the subscriber's phone is not answered within a predetermined number of rings). The softswitch determines that the call is for a subscriber, determines the subscriber identity, accesses the subscriber's account configuration (e.g., which includes some or all of the following: subscriber call processing, transfer, screening instructions, subscriber work and home fixed phone addresses, mobile phone address, information identifying information related to one or more telecommunications clients associated with the subscriber, etc.).

At state 304, the softswitch recognizes that the subscriber's telecommunications client is online (e.g., via a communication from the client to the softswitch) and that the caller is not one of the subscriber's VIP contacts (e.g., a caller that has been designated as a priority or preferred caller by the subscriber, wherein the designation has been stored and is now retrieved from a database). Therefore, the softswitch presents the call at the telecommunications client and begins the screening process using a half-duplex talk path, as similarly described above. If the caller was a VIP contact, the softswitch is optionally configured to provide special call treatment. For example, in response to a subscriber-specified configuration, the softswitch can bypass screening and immediately provide a full-duplex talk path on answer, or the softswitch substantially simultaneously ring multiple subscriber communication devices (e.g., the subscriber's mobile and fixed phone) without answering/screening the call, and if that failed (e.g., the mobile or fixed phones were not answered), a message from the VIP caller can then be recorded (or, if so pre-configured by the subscriber, the softswitch can try still another communication device, such as a VoIP phone associated with the subscriber) for later retrieval by the subscriber.

At state 305, the subscriber decides to take the call on the subscriber's mobile phone (e.g., because the subscriber is about to leave the office or other location), and so provides a corresponding instruction to the softswitch (e.g., by activating a “take call on mobile phone” menu selection presented on the telecommunications client or otherwise). As discussed below, FIG. 35 illustrates an example user interface via which the subscriber can specify where a call is to be taken.

At state 306, the softswitch recognizes the instruction issued by the subscriber via the client and so dials the mobile phone. The call is optionally delivered to the mobile phone via the PSTN, MSC, and BS.

At state 307, the subscriber answers the mobile phone, and a two-way talk path is established with the caller by the softswitch so that the caller and subscriber can converse.

Of course, other destination options can optionally be presented to the subscriber in the above process. For example, the telecommunications client may provide “take the call” menu selections that include: mobile phone, work landline phone, home landline phone, VoIP phone, etc. If, for example, the subscriber selected the “take the call at home phone” menu selection (or otherwise requested to take the call at home), the softswitch responds by routing the call to the subscriber's fixed, home phone.

FIG. 34 illustrates a user interface. In this example, the user interface displays a message (“ready for calls” that indicates when the client application is ready to place or receive calls. FIG. 35 illustrates the user interface of FIG. 34, except in this example, an incoming call has been received by the softswitch. The user interface displays caller identification information for the caller (e.g., callerID/name information obtained by the softswitch from call signaling information and/or otherwise obtained or derived), and a menu of destinations via which the subscriber can instruct the softswitch as to where the subscriber wants to take the call (e.g., “my phone (805-690-4104)”, “on cell phone (805-637-0280).

FIG. 30 illustrates example system components involved in providing BCM Mobile/Fixed One-Number functionality. In this example, the softswitch integrates with the wireless network in an MVNO relationship. This enables the phone number to be owned by a third party, such as a SIP service provider yet be associated with the mobile phone in the wireless network, so that calls, SMS messages, and/or MMS messages from that mobile phone are identified by the assigned phone number. The assigned phone number can be from a pool associated with the softswitch operator, or the phone number can be the subscriber's original mobile phone number that has been ported to the third party.

Optionally, the assigned phone number assigned becomes the “one number” or VTN that can be used to reach the subscriber at multiple lines, such as, by way of example, via a mobile phone, a fixed phone, a VoIP phone, or the telecommunications client. Optionally, the VTN is published as the caller ID (e.g., inserted into a callerID field in call signaling associated with calls placed using these devices so that calls appear to originate from the same phone number even when the call actually originates from different phones associated with different phone lines or carriers.

Referring again to FIG. 30, an example call scenario is illustrated in which a caller initiates a call to a VTN associated with a mobile phone. The call is received by the softswitch. The softswitch determines that the call is for a subscriber, identifies the subscriber owning or associated with this VTN, accesses the subscriber's account configuration (e.g., which includes some or all of the following: subscriber call processing, transfer, screening instructions, subscriber work and home fixed phone addresses, mobile phone address, information identifying information related to one or more telecommunications clients associated with the subscriber, etc.). Based on the subscriber account configuration, the softswitch routes the call to the mobile phone.

At state 401, a caller dials the phone number assigned to the mobile phone. At state 402, the phone number is recognized in the PSTN as owned by a SIP service provider or other third party, and so the call is routed to the SIP service provider switch serving that number.

At state 403, the SIP Proxy associated with the SIP provider converts the PSTN call to SIP (or other desired protocol) and transmits a message to the softswitch informing the softswitch of the call. At state 404, the softswitch queries the HLR to get the status of the mobile phone so that the Softswitch can determine how to handle the call.

At state 405, the HLR in turn queries the Visitor Location Register (VLR) of the MSC currently serving the mobile phone to determine its status and location. At state 406, the softswitch receives an indication that the mobile phone is accessible (e.g., on and in communication with a base station), and so the softswitch routes the call through the PSTN to the MSC serving the mobile phone in the given wireless network.

At state 407, the MSC consults its VLR for the current location of the subscriber's mobile phone so that it can route the call to the specific Base Station (BS) serving the phone.

At state 408, the BS delivers the call to the mobile phone and the subscriber answers. This causes an Answer indication to be propagated back through the networks to the softswitch. When the softswitch receives the Answer indication from the mobile phone, the softswitch opens a channel to the voice mail subsystem and establishes a one-way talk path so that the person answering the phone can screen the call while a message is being recorded.

At state 409, while delivering the call to the mobile phone, the softswitch delivers the call to the subscriber's work computer-based client application, with screening. At state 410, the person that answered the phone keypresses 1 (or provides other appropriate input) to take the call. When the softswitch detects the DTMF signal, the softswitch ends the recording and opens up a two-way talk path between the two parties so that they can converse.

While the call is active, the person answering the phone has the option of taking the call/end screening (e.g., by keypressing 1 or providing other appropriate input), transferring the call to a fixed phone (e.g., a home landline phone that may be shared with other members of the household) or another phone (e.g., by keypressing 2 or providing other appropriate input), or conferencing in other parties (e.g., by keypresses 3 or providing other appropriate input). If the mobile phone had been unavailable (e.g., had been turned off or was busy), the softswitch would know this from the response to its HLR query and would act appropriately to deliver the call to the subscriber's fixed phone (or other designated terminal) instead. The owner of the mobile phone is notified of missed calls via the phone's message waiting icon, SMS, MMS, email, or other communication technique, as desired.

When a call is originated from a mobile phone, the call is optionally routed through the softswitch to give the subscriber call transfer and conferencing feature control the same as, or similar those provided to the subscriber on inbound calls. FIG. 31 illustrates an example process of how external calls from the fixed phone can also be routed through the softswitch to provide enhanced call management functions and to ensure that the assigned number gets used as the caller ID associated with the subscriber's call. The call in this example is initiated by the subscriber via the subscriber's telecommunication client or browser. The softswitch dials the fixed phone. When the fixed phone starts ringing, the softswitch dials the Callee phone to bridge the two phones together. In particular, referring to FIG. 31, an example call handling process is as follows.

At state 501, the subscriber selects a contact (e.g., via the subscriber's contact database/electronic address book accessed via a telecommunications application hoisted on the subscriber's computer, via a browser which accesses the contacts hosted on the softswitch, or otherwise) and clicks a Call button (e.g., displayed and accessed via the client application, the browser, or otherwise).

At state 502, the call request passes through the corporate firewall to the softswitch (e.g., over a client session). The softswitch access the account configuration associated with the subscriber (e.g., which includes some or all of the following: subscriber call processing, transfer, screening instructions, subscriber work and home fixed phone addresses, mobile phone address, information identifying information related to one or more telecommunications clients associated with the subscriber, etc.).

At state 503, to establish the one end of the call, the softswitch dials the fixed phone number (using the fixed phone address accessed from the account configuration) causing it to ring. If needed, two-staged dialing is used to get through the Auto Attendant, although DID can be used as well.

At state 504, once the subscriber's fixed phone is answered, the softswitch dials the Callee via the SIP connection to the SIP provider. The subscriber's assigned phone number (e.g., assigned VTN) is used as the caller ID (e.g., is inserted into the callerID signaling field associated with the call to the Callee). The softswitch bridges the two ends of the call together.

At state 505, the SIP provider converts the call to SS7 signaling (including the assigned phone number in the callerID field) as needed to cause the call to be routed to the Callee's phone. The assigned number (e.g., the subscriber's VTN) is displayed in the Callee's caller ID display. The Callee answers the phone, a full duplex talk path is established, and the Callee and subscriber begin conversing.

At state 506, while talking, in this example the subscriber needs to head to a meeting, and so presses 2 (or other designated input) on the fixed phone to transfer to the mobile phone and continue the conversation while heading for the meeting.

At state 507, the softswitch detects the DTMF signal corresponding to the subscriber's keypress, and queries the HLR to determine the mobile phone status. From the status of the subscriber's phones, the softswitch infers that the subscriber wishes to transfer the call to the mobile phone. At state 508, the softswitch delivers the call to the mobile phone via the PSTN, MSC, and BS.

At state 509, the subscriber answers the mobile phone. At this point the Callee, the mobile phone, and the fixed phone are temporarily conferenced together until the subscriber hangs up the fixed phone and converses with the Caller using the mobile phone.

Optionally, the subscriber could have made the call directly from the fixed phone by speed dialing or otherwise dialing to the softswitch and then entering the number of the Callee. Optionally, the softswitch can voice prompt the subscriber to select the Callee (e.g., “Name Please”), and the subscriber then selects who is to be called using a voice command (e.g., “Bob” or other Callee identifier). The subscriber can also have originated a call via a mobile phone. A call origination from the mobile phone optionally similarly makes use of the subscriber's contact list/electronic address book to make a call with a voice command (e.g., interpreted by the phone's internal speech recognition capability, by the softswitch or otherwise), or the Callee can be identified via keypresses or a menu selection.

Example mobile answering services and functionality will now be described. A business or other customer registers for a Mobile Answering service by going to a BCM landing page (e.g., a web page available at a corresponding URL and associated with the softswitch operator, provider or a related entity) using a browser or other interface, and supplying requested information in corresponding Web page form fields. The table below the data below describes example data, some or all of which may be requested.

TABLE 4 Mobile Answering Registration Data Requested and/or Required Data Information? Description Mobile Yes The phone number of the mobile device the phone customer uses for work (or other specified number location). Optionally, it is assumed that this device is for the subscriber's own personal use and not shared with others. Wireless Yes The carrier servicing this mobile phone carrier number. A drop down list is provided, with the default being the carrier inferred from the LERG database. Password Yes Numeric or other password used to access Mobile Zone from point other than the customer's PC Client and used to access Phone Client when accessed from phone other than the subscriber's mobile phone. Email No The customers work email address (or other address specified email address, such as a personal email address).

In an example, process, once the requested data provided by the subscriber is received and recorded in computer readable memory, an account with the BCM-MA package offer is created. The subscriber is then asked to forward the subscriber's phone to a specified phone number associated with the softswitch (or other designated destination) to initiate service. The mobile phone number provided is used to determine who the associated carrier is, and to present carrier-specific instructions for reprogramming the call forwarding. Optionally included with this information is an indication as to whether charges on the subscriber's phone bill for forwarded calls will occur or are likely. Assurances can optionally be provided to the subscriber that the forwarding change can be easily undone if necessary or desired and the softswitch operator or agent will help undo the forwarding change.

By way of example, the subscriber may be requested to forward the subscriber's calls to a phone number associated with the softswitch operator or agent, such as a 775-665-1234 pilot number, unless the carrier is known to not support including the caller ID as part of the call information when forwarding a call. In this case, the subscriber is assigned a personal 775-665-1234 VTN.

If a telecommunications client is to be used to access services, the subscriber is requested to download the telecommunications client. For example, the subscriber can be provided with a download link via which the client can be downloaded. In an example embodiment, once downloaded, the client optionally presents a registration form, wherein the subscriber re-enters some or all the data referred to in Table 1, and then the subscriber is presented with a user interface (e.g., a web page) that asks whether the subscriber has forwarded the subscriber's phone to the specified phone number associated with the softswitch (or other specified destination). If not, the subscriber is provided with instructions on how to have calls forwarded to the designated destination.

After the subscriber indicates that the forwarding change has been completed, an automated test call is made to the subscriber's mobile phone to verify the call forwarding is working. For example, shortly before the test is performed, the subscriber is optionally instructed to let the mobile phone ring (e.g., when the test call is placed) so that the call will automatically forward to the softswitch (or other designated destination). The softswitch will then cause the subscriber's telecommunication client to present the call and screen a prerecorded message (e.g., “Your phone line is now configured to forward calls to our call processing system) that is left by the test program. The call optionally then appears in the subscriber's call log (e.g., presented via the telecommunications client or via a browser). Optionally, no entry in the contact list is generated. If the test fails, diagnostic information is displayed indicating the likely cause and actions to take, which may be to call Customer Care for assistance.

Optionally, the subscriber is also encouraged to install the telecommunication client on other subscriber computers (e.g., the subscriber's home computer, laptop computer, etc.) so that the subscriber can access the subscriber's call log and review the subscriber's messages at different locations.

The registration process optionally concludes with a thank you message and instructions about how to use the phone client to create a personal greeting, retrieve messages, and/or configure the subscriber's phone processing services. By way of example, the phone client is optionally accessed by dialing the assigned designated number (e.g., a 775-665-1234 pilot number) or the subscriber's VTN. Optionally, the subscriber is advised to set up a speed dial key (e.g., ‘1’) on the subscriber's mobile phone for accessing the phone client. Customer Care contact information is optionally prominently displayed via the subscriber's telecommunications client or other user interface, to provide with the subscriber with simple access to support personnel who can process subscriber requests (e.g., help requests, undo call forwarding requests, etc.).

If an email address was entered via the registration user interface, the thank you notification and Phone Client instructions are optionally also or instead emailed to the subscriber.

When the account is created for the subscriber, SMS call notification is optionally enabled, and optionally, the subscriber can disable SMS call notification. Email call notification with message attachment is optionally also enabled if an email address was entered, wherein such notification and attachment can be configured by the subscriber. Email notification is optionally disabled automatically after the first telecommunication client session with the softswitch, although optionally the subscriber can re-enable it via the Mobile Zone or other designated Web page or user interface.

As similarly discussed elsewhere herein, a subscriber can be notified of calls (e.g., via SMS, MMS, instant message, and/or email). If an SMS messaging is to be used, an SMS gateway used for routing notifications is optionally automatically configured based on the wireless carrier information gathered during registration. Optionally, by default, SMS notification is enabled for calls with messages. Optionally, by default, SMS notification is disabled for calls with messages. From the Mobile Zone website or other user interface, the subscriber can also enable/disable SMS notification (or other notification) for calls without messages and notification via email. For notifications via email, the subscriber has the option of specifying via one or more of the user interface described herein that the message (e.g., in the form of an audio file) is to be attached to emails sent to the subscriber. The email address for notification optionally defaults to the email address specified during registration but can be changed by the subscriber using one or more of the user interfaces described herein. When an email address is changed, the subscriber optionally is asked whether the new email address is also to be used as the subscriber's contact address for account matters, service notifications, and other communications.

A call notification (e.g., via SMS, MMS, email, instant messaging, etc.) includes one or more of the time of the call, the caller's phone number, the caller's name as determined from the contact list or caller name service, and/or an indication as to whether or not a message was left. A call notification via email includes optionally includes the message as well.

As discussed elsewhere herein, the softswitch optionally maintains a log of calls received by the softswitch for the subscriber (e.g., calls forwarded to the softswitch from the subscriber's mobile phone). The call log may be available to the subscriber via one or more user interfaces (e.g., a phone client, a telecommunications client hosted on a subscriber computer, a Web site, such as the Mobile Zone). For example, the call log information can include some or all of the following: call date/time, call duration, caller's phone number, caller's name, caller's phone service location (e.g., city, state), caller's phone type (home, work, mobile, fax, other), voice message duration, link to voice message, number of fax pages, link to fax pages. Other embodiments may log less, more, or different information. Further, the availability of information via the various platforms may be different for different user interfaces. For example, optionally, less log data is made available via the phone client than via the Mobile Zone. Optionally, all, or a subset of the data can be accessed via the phone client, the telecommunications, and/or the Mobile Zone.

Optionally, a Menu button is provided on the telecommunications client application which can be used by a subscriber to set preferences and to access the Mobile Zone for feature settings (optionally, broader feature settings may be made available via the Mobile Zone than via the telecommunications client application). The preference settings optionally include which sound is to be played when presenting a call, whether to play a beep on the host computer speaker if a number client using the client application is busy, and whether the speaker is to be muted by default for incoming calls. Optionally, a user interface is provided that enables a subscriber to alter the subscriber's name, email address, and/or password.

The following table provides a description of various fields and corresponding descriptions for an example contact list entry for a given contact phone number. Other embodiments can have fewer, additional, or different fields. The subscriber's contact list is optionally displayed when a telecommunications client user interface Contacts tab is selected. A contact entry is optionally displayed on one or more lines, wherein additional lines may be used to display multiple phone numbers for a contact.

Data Description Name Name associated with the contact's phone number in the subscriber's contact list. If no name is provided, the name field optionally displays the phrase “Unknown” or other like, or is blank. “Unknown” entries are optionally listed first. “Unknown” entries are optionally listed last. If this row is not the first phone number for this contact, then the name field is left blank/not provided. Phone number Phone number of the contact. Phone number e.g., home, work, mobile, fax, VoIP, or Other icon type indicating the phone type. Email address The contact's email address, which if non-empty, is optionally a hyperlink to a send mail page. If this row is not the first row for this entry, then email address is left blank/not provided. Membership A row displays a service provider icon if a phone number of a BCM or Prepaid account matches the phone number in the phone number field.

FIG. 32 illustrates an example display of a contact list including a plurality of entries.

Thus, as described above, certain embodiments facilitate caller access to a subscriber by enabling a caller to call a certain phone number, wherein the call can be routed to the subscriber's current local telephone. Thus, for example, a caller can reach the subscriber at work, at home, via the subscriber's mobile phone using the same phone number. Similarly, the subscriber can place a call using different phones, such as the subscriber's work, home, or mobile telephones, and have the same number published to the called parties,

It should be understood that certain variations and modifications of this invention would suggest themselves to one of ordinary skill in the art. The scope of the present invention is not to be limited by the illustrations or the foregoing descriptions thereof.

This application incorporates by reference in their entirety the contents of U.S. Pat. No. 7,688,958 (titled “METHODS AND APPARATUS FOR PROVIDING EXPANDED TELECOMMUNICATIONS SERVICE”) and U.S. Pat. No. 8,107,609 (titled “METHODS AND SYSTEMS FOR TELEPHONY CALL-BACK PROCESSING”) 

1. (canceled)
 2. A system, comprising: at least one networked computing device comprising hardware; a network interface; non-transitory memory that stores instructions that when executed by the at least networked one computing device cause the system to perform operations comprising: enable instances of a software application to be downloaded over at least one data network to, and installed on a first plurality of computing devices associated with a same user, wherein the downloaded software application instances reside behind a firewall of at least a portion of the first plurality of computing devices; receive a software application instance initiated presence communication over at least one data network from a plurality of the first plurality of computing devices associated with the user on which an instance of the software application is installed; store in non-transitory computer memory an online state indication for each of the first plurality of computing devices associated with the user from which the software application instance initiated presence communication is received; and for each of the first plurality of computing devices associated with the user and associated with an online state indication, enable, at least in part, an incoming call notification to be synchronously displayed by a user interface of the installed instance of the software application, wherein the user interface of the installed instance of the software application further provides a control enabling a user to block a call associated with the incoming call notification.
 3. The system as defined in claim 2, wherein the first plurality of computing devices comprises a mobile phone and a laptop computer, wherein the incoming call notification comprises at least one of a phone address associated with a calling party or a name associated with the calling party, and wherein the instructions, when executed by the at least networked one computing device cause the system to perform operations further comprising synchronize contact record changes for each of the first plurality of computing devices associated with the user on which the software application is installed.
 4. The system as defined in claim 2, wherein the first plurality of computing devices comprises a mobile phone.
 5. The system as defined in claim 2, wherein the at least one data network comprises the Internet.
 6. The system as defined in claim 2, wherein an incoming call associated with the incoming call notification comprises a Public Switched Telephone Network (PSTN) call.
 7. The system as defined in claim 2, wherein an incoming call associated with the incoming call notification comprises a Voice over Internet Protocol (VoIP) call.
 8. The system as defined in claim 2, wherein the incoming call notification comprises a phone address associated with a calling party.
 9. The system as defined in claim 2, wherein the incoming call notification comprises a name accessed from a contact data store associated with the installed instance of the software application.
 10. The system as defined in claim 2, wherein the instructions, when executed by the at least networked one computing device cause the system to perform operations further comprising: in response to a change to a contact record associated with an installed instance of the software application on a computing device of the first plurality of computing devices, synchronize the contact record change for each of the first plurality of computing devices associated with the user on which the software application is installed.
 11. The system as defined in claim 2, wherein answering of an incoming call associated with the call notification is inhibited if the block call control is selected by the user.
 12. A system, comprising: at least one networked computing device comprising hardware; a network interface; non-transitory memory that stores instructions that when executed by the at least networked one computing device cause the system to perform operations comprising: receive a software application instance initiated presence communication over a data network from each of a first plurality of online computing devices associated with a same user for which an instance of a call management software application is installed, wherein one or more instances of the installed call management software application is behind a firewall; store in non-transitory computer memory an online state indication for each of the first plurality of computing devices associated with the user from which the receipt of the software application instance initiated presence communication is received; and for each of the first plurality of computing devices associated with the user and associated with an online state indication, enable, at least in part, an incoming call notification to be synchronously displayed by a user interface of the installed instance of the software application, wherein the user interface of the installed instance of the software application further provides a control enabling a user to block a call associated with the incoming call notification.
 13. The system as defined in claim 12, wherein a computing device of the first plurality of online computing devices comprises a mobile phone.
 14. The system as defined in claim 12, wherein the data network comprises the Internet.
 15. The system as defined in claim 12, wherein an incoming call associated with the incoming call notification comprises a Voice over Internet Protocol (VoIP) call.
 16. The system as defined in claim 12, wherein the incoming call notification comprises a phone address associated with a calling party.
 17. The system as defined in claim 12, wherein the incoming call notification comprises a name accessed from a contact data store associated with the installed call management software application.
 18. The system as defined in claim 12, wherein the instructions, when executed by the at least networked one computing device cause the system to perform operations further comprising: in response to a change to a contact record associated with an installed call management software application on a computing device of the first plurality of computing devices, synchronize the contact record change for each of the first plurality of computing devices associated with the user on which the call management software application is installed.
 19. The system as defined in claim 12, wherein answering of an incoming call associated with the call notification is inhibited if the block call control is selected by the user.
 20. A system, comprising: at least one networked computing device comprising hardware; a network interface; non-transitory memory that stores instructions that when executed by the at least networked one computing device cause the system to perform operations comprising: enable instances of a software application to be downloaded over at least one data network to, and installed on a first plurality of computing devices associated with a same user, wherein the downloaded software application instances reside behind a firewall of at least a portion of the first plurality of computing devices; receive a software application instance initiated presence communication over at least one data network a plurality of the first plurality of computing devices associated with the user on which an instance of the software application instance is installed; store in non-transitory computer memory an online state indication for each of the first plurality of computing devices associated with the user from which the software application instance initiated presence communication is received; and for each of the first plurality of computing devices associated with the user and associated with an online state indication, enable, at least in part, an incoming call notification to be synchronously displayed by a user interface of the installed instance of the software application.
 21. The system as defined in claim 20, wherein the incoming call notification comprises a name accessed from a contact data store associated with the installed instance of the software application.
 22. The system as defined in claim 20, wherein the instructions, when executed by the at least networked one computing device cause the system to perform operations further comprising: in response to a change to a contact record associated with an installed instance of the software application on a computing device of the first plurality of computing devices, synchronize the contact record change for each of the first plurality of computing devices associated with the user on which the software application is installed. 